• #A
    #B
    #C
    #D
    Explanation:
    Calldata is immutable and cannot be modified by the callee. This makes it gas-efficient and safe for external function inputs
  • #A
    #B
    #C
    #D
    Explanation:
    Changing variable types alters how Solidity packs them into storage slots. This can shift offsets and corrupt existing storage layouts in upgradeable contracts.
  • #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.
  • Hasan Rasheed

    Hasan Rasheed

    @9LmOKUb3w

    From CFO back to 0x

    In 2019, I joined Xord as an initial member and a Frontend Dev. We were small, hungry, and building. But as we scaled to 3 countries, the "business" side got...
    1
    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.
  • #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.
  • #A
    #B
    #C
    #D
    Explanation:
    The override keyword forces explicit acknowledgment when a derived contract replaces a parent variable or function. This prevents accidental state variable shadowing in inheritance hierarchies, which can otherwise lead to subtle storage corruption bugs.
  • #A
    #B
    #C
    #D
    Explanation:
    Without the virtual keyword, a function cannot be overridden in derived contracts. This breaks the override chain and prevents proper polymorphic behavior in multiple inheritance scenarios.
  • #A
    #B
    #C
    #D
    Explanation:
    pure functions cannot read blockchain context such as msg.sender or block.timestamp. They are restricted to computation based solely on input parameters and local variables
  • Application deadline: 2 days
    A

    Founding Product Designer

    AlliumFULL_TIMENA

    Job description
    Allium builds infrastructure to make blockchain data accurate, standardized, and accessible at scale. The company ingests and normalizes large volumes of on-chain data across more than 100 blockchains, serving analysts and engineers who rely on reliable, near–real-time data for analytics and application backends. As the Founding Product Designer, this role...
  • 1
    Replies
  • Application deadline: 3 weeks
    Job description
    Senior Frontend Engineer — React / TypeScript — Global — Remotebuilds financial infrastructure and products for the stablecoin economy, including a widely used multisig platform on Solana. This remote web3 role focuses on owning the frontend experience for secure, high-performance web applications used by treasury teams, validators, and protocol operators...
  • #A
    #B
    #C
    #D
    Explanation:
    If a modifier reverts after the _ placeholder executes, the entire transaction is reverted. All state changes made inside the function and modifier are rolled back due to Ethereum’s atomic execution model.
  • #A
    #B
    #C
    #D
    Explanation:
    An uninitialized storage pointer defaults to storage slot zero. This can overwrite critical state variables such as ownership or balances, making it a high-severity audit issue.
  • 0
    Replies
Home Channels Search Login Register