For developers

Docs

Every address, parameter and event, straight from the same configuration the app runs on. The human explanation lives in How it works.

The smart contract

GiftEscrow smart contract0x0dc1a5c1d6168862727318c22058a8df980192e3

Deployedblock 115,508,479 on BNB Smart Chain

Custodythe smart contract holds every escrowed share; no person and no server can move them

Protocol fee1% at creation, with a hard cap written into the smart contract so it can never be raised

Everything this product promises is enforced by this one smart contract: it escrows the share the moment a gift is created, checks the claim signature, enforces the slippage floor, and pays out claims and refunds. The site and the relayer only read from it and hand it transactions; neither can override what it decides. Anything described in these docs can be checked against the deployed code on BscScan.

Network

ChainBNB Smart Chain · id 56

PancakeSwap SmartRouter0x13f4EA83D0bd40E75C8222255bc855a974568Dd4

PancakeSwap V3 factory0x0BFbCF9fa4f9C56B0F40a671Ad40E0805A091865

PancakeSwap V3 quoter0xB048Bbc1Ee6b733FFfCFb9e9CeF7375518e25997

Chainlink BNB / USD0x0567F2323251f0Aab15c8dFb1967E4e8A7D42aeE

bStocks pause manager0x9fc74Be63f3589485B2423984a7a0557e0CF700a

bStocks compliance0x53dBa7AaBDe774787A1F57236B235567dA8e14F4

Every address was read onchain before being written down. The pause manager and compliance registry are the issuer's controls: both are checked before any transaction is submitted, because a paused token or a blocked address would otherwise burn gas on a doomed claim.

Listed tokens

NVDA

NVDAB

token: 0x02Fca66C1D1aFB4E2A7884261eB00F63598a7436
feed: 0xea5c2Cbb5cD57daC24E26180b19a929F3E9699B8

TSLA

TSLAB

token: 0x5b1910eAaD6450E50f816082Aa078C41F10C292f
feed: 0xEEA2ae9c074E87596A85ABE698B2Afebc9B57893

AAPL

AAPLB

token: 0x431a3BEE82E2ca41e49895CbECE5bB0F76A89b7A
feed: 0xb7Ed5bE7977d61E83534230f3256C021e0fae0B6

MSFT

MSFTB

token: 0x80106cb3EAD06659A5ad19DF39D9b4733863B9b0
feed: 0x5D209cE1fBABeAA8E6f9De4514A74FFB4b34560F

GOOGL

GOOGLB

token: 0x3F53De71c126BdaBAe20f9cD64848d317f6C3238
feed: 0xeDA73F8acb669274B15A977Cb0cdA57a84F18c2a

Parameters

Gift size$1 to $5,000

Splits per giftup to 100

Expiry30 days, then anyone can return it to the sender

Slippage tolerance1.0%, contract enforced

Max price impact3.0%, or the route is refused

Max price divergence5.0% between Chainlink and the pool

Max price age3 days, covering weekends when equity feeds sleep

Min pool depth$10,000 quote-side

Pool fee tiers0.01% · 0.05% · 0.25% · 1%

Claim protocol

Creating a gift generates a fresh keypair in the sender's browser. The public address goes onchain as the gift's claim key; the private half goes after the # in the link and never reaches a server.

To claim, the receiver's browser signs exactly one message with that key: a digest binding the receiver's wallet address, the chain id and the address of the escrow smart contract. The relayer submits the transaction and pays the gas. Because the signature commits to one recipient on one deployment, it cannot be redirected or replayed anywhere else.

Relayer endpoint

POST /api/claim

{
  "claimKey":  "0x…",  // the gift's public claim address
  "recipient": "0x…",  // the wallet receiving the share
  "signature": "0x…"   // 65-byte signature over the digest
}

The relayer preflights everything it can read: gift status, expiry, issuer pause state and the compliance registry, and simulates the claim before spending gas. A request that would fail onchain is rejected with the reason instead of submitted.

Events

GiftCreatedemitted once per gift, with the escrowed token and amount

GiftClaimedemitted per claimed share, with the recipient

GiftRefundedemitted when a gift returns to its sender

All three are public on BscScan, so anything this site claims can be recounted from the chain.