• Application deadline: 3 days
    T

    Web3 Blockchain Engineer – ERC-4626 Vault Router

    Token MetricsFULL_TIMENA

    Job description
    Token Metrics builds crypto-focused analytics and infrastructure products used by investors and portfolio managers across global markets. This contract role sits within the engineering team and focuses on developing EVM-based smart contract infrastructure, including work related to ERC-4626 vault routing. As a Web3 Blockchain Engineer, you will collaborate closely with...
  • Application deadline: 3 days
    P

    Smart Contract Engineer

    Paxos LabsFULL_TIMENA

    Job description
    Paxos Labs builds enterprise-grade onchain infrastructure used by large financial organizations to support transparent and verifiable digital asset products. The Smart Contract Engineer role sits within the engineering organization and focuses on scaling the company’s DeFi protocol infrastructure. The position involves researching, designing, and implementing core protocol mechanisms across areas...
  • Application deadline: 3 days
    C

    Smart Contract Engineer

    Category Labs (formerly Monad Labs)FULL_TIMENA

    Job description
    Category Labs is a systems engineering and research team building high-performance decentralized infrastructure. The company focuses on application-layer primitives enabled by a custom, high-throughput EVM client. As a Smart Contract Engineer, you will work within the core engineering group to design and implement smart contracts aligned with the performance characteristics...
  • 2
    Replies
  • 2
    Replies
  • 2
    Replies
  • #A
    #B
    #C
    #D
    Explanation:
    EXTCODESIZE returns zero for EOAs and non-zero for deployed contracts. This distinction is commonly used for contract detection, though it has edge cases.
  • 3
    Replies
  • #A
    #B
    #C
    #D
    Explanation:
    GASLEFT returns the amount of gas remaining in the current execution context. It is commonly used for gas-aware logic and debugging.
  • #A
    #B
    #C
    #D
    Explanation:
    bytes32 always occupies a full 32-byte storage slot. Smaller types may be packed together, but bytes32 always stands alone.
  • 3
    Replies
  • #A
    #B
    #C
    #D
    Explanation:
    Solidity packs struct variables tightly into storage slots based on declaration order. Reordering fields can change slot boundaries and break upgrade compatibility.
  • 3
    Replies
  • #A
    #B
    #C
    #D
    Explanation:
    The base slot of a mapping is derived using keccak256(key . slot). This hashing ensures unique storage locations per key without collisions.
  • 6
    Replies
Home Channels Search Login Register