viraj124

I am a crypto dev with around 7 years of experience and 8 years of professional experience overall, I built and shipped backend systems and smart contracts with 100% test coverage and multiple audits managing $100M in TVL at peak at projects like fuel labs, camp network, Shell Protocol, GoodGhosting, Instadapp, Juicebox Dao etc and also handled some product management in some of these roles.

I have led engineering teams in a few of these roles as well

Recently have also been using AI tools like Claude and Codex and shipped different dApps like https://flexfun.app/ and https://agenticbets.dev/

I also have experience as a security researcher teaming for audit contests and private audits in evm and solana codebases

Fintech is one of the reasons I got in the Blockchain Industry as a builder and over the years have had a good amount of experience working on DeFi projects and Working at Blend would be a good opportunity to work in the intersection between TradFi and DeFi and I feel I am a good fit for this role

viraj124

My public address us 0x120748E0ED080F94DFC90E8Aca4E107c250B8c67

viraj124

import fs from 'fs'
import csv from 'csv-parser'

const json: any = []
fs.createReadStream('scripts/input.csv')
  .pipe(csv())
  .on('data', (row: any) => {
    const val: any = Object.values(row)[0]
    json.push(val)
  })

viraj124

// File: @openzeppelin/contracts/utils/Context.sol


pragma solidity >=0.6.0 <0.8.0;

/*
 * @dev Provides information about the current execution context, including the
 * sender of the transaction and its data. While these are generally available
 * via msg.sender and msg.data, they should not be accessed in such a direct
 * manner, since when dealing with GSN meta-transactions the account sending and

viraj124

// File: @openzeppelin/contracts/utils/Context.sol


pragma solidity >=0.6.0 <0.8.0;

/*
 * @dev Provides information about the current execution context, including the
 * sender of the transaction and its data. While these are generally available
 * via msg.sender and msg.data, they should not be accessed in such a direct
 * manner, since when dealing with GSN meta-transactions the account sending and

viraj124

pragma solidity ^0.6.0;


// very simple version of the wallet contract
contract Wallet {
    
    // this doesn't have a authentication layer since it is an example ideally which ever user is the owner of this wallet can only call this method
    function execute(address _target, bytes memory _data)
    public
    payable

viraj124

pragma solidity ^0.6.0;


contract Box {
    uint256 private value;

    // Emitted when the stored value changes
    event ValueChanged(uint256 newValue);

    // Stores a new value in the contract

viraj124

// SPDX-License-Identifier: MIT
pragma solidity ^0.6.0;

import "https://raw.githubusercontent.com/OpenZeppelin/openzeppelin-contracts/master/contracts/utils/Create2.sol";

contract MinimalProxyFactory {
    event MinimalProxyCreated(address minimalProxy);

    function computeAddress(uint256 salt, address implementation)
        public

viraj124

import _ from 'lodash';
import { QueryParams } from 'routing-controllers';
import { Service } from 'typedi';

import { ApiPromise, WsProvider } from '@polkadot/api';
import { Keyring } from '@polkadot/keyring';

import { StakingOperatioQuery } from '../controllers/requests/StakingQuery';

viraj124

import * as bip32 from 'bip32';
import * as BufferLayout from 'buffer-layout';
import _ from 'lodash';
import nacl from 'tweetnacl';
import { Service } from 'typedi';

import {
    Account, Connection, PublicKey, SystemProgram, SYSVAR_RENT_PUBKEY, Transaction,
    TransactionInstruction
} from '@solana/web3.js';