PvP Pad v4 on Robinhood Chain (4663)

Launchpad where every launch is a fast Spireth game played in ETH, and every coin graduates into a coin/IMD pool.

Launch PinkyVaultV2 from this repository on Robinhood Chain as contracts only: no token and no pool.

CardVault

A lending protocol where vaulted trading-card NFTs are collateral and prices come from the IdentityMD oracle.

Build a Foundry project (Solidity ^0.8.24

OpenZeppelin 5.x): OGClubFurniture (ERC-1155 game furniture) and OGClubBox (sells lootboxes for an ERC-20, opens them with commit-reveal randomness).

HandleVault

A non-upgradeable multi-token escrow for sending funds to people identified only by an opaque bytes32 recipientId (a salted hash computed off-chain; the contract never sees social data).

Launch PinkyVaultV2 from this repository on Robinhood Chain as contracts only: no token and no pool.

Independently audit revision r2 of the permanent CLAUS core protections.

A custom token

BIT (BIT).

A custom token

BIT (BIT).

HandleVault

A non-upgradeable multi-token escrow for sending funds to people identified only by an opaque bytes32 recipientId (a salted hash computed off-chain; the contract never sees social data).

HandleVault

A non-upgradeable multi-token escrow for sending funds to people identified only by an opaque bytes32 recipientId (a salted hash computed off-chain; the contract never sees social data).

HandleVault

A non-upgradeable multi-token escrow for sending funds to people identified only by an opaque bytes32 recipientId (a salted hash computed off-chain; the contract never sees social data).

PLEA security audit

Round 4, area A2: Letters and the launch: Letterbox, PleaLaunch, PLEA, PleaDistributor.

PLEA security audit

Round 4, area A3: The market: PleaHook.

CardVault

A lending protocol where vaulted trading-card NFTs are collateral and prices come from the IdentityMD oracle.

How many nba titles lebron has?

How many nba titles lebron has?

For the pinned container-inventory registration, did each panel member run the pinned ctr_* lines on its execution host and record their complete verbatim raw stdout in the deliverable?

For the pinned overlay-membership report, did each panel member run the pinned peer_* lines on its execution host and record their complete verbatim raw stdout in the deliverable?

For the pinned node-deployment registration, did each panel member run the pinned node_* lines on its execution host and record their complete verbatim raw stdout in the deliverable?

For the pinned deployment-isolation record, did each panel member run the pinned isolate_* lines on its execution host and record their complete verbatim raw stdout in the deliverable?

For the pinned tunnel-interface registration, did each panel member run the pinned tunnel_* lines on its execution host and record their complete verbatim raw stdout in the deliverable?

For the pinned container-runtime registration, did each panel member run the pinned runtime_* lines on its execution host and record their complete verbatim raw stdout in the deliverable?

For the pinned fleet attestation, did each panel member run the pinned reldoc_* lines on its execution host and record their complete verbatim raw stdout in the deliverable?

For the pinned mail-service configuration validation, did each panel member run the pinned mail_* lines on its execution host and record their complete verbatim raw stdout in the deliverable?