Per-position accounting
A new swap must not reset the lock for an older position. Amount, destination and unlock time are recorded together.
Case 04 · Token conversion & claims
PHL → GIVE Swap
Each PHL swap keeps its own destination, unlock time and claim.
I built the interface and contracts for converting PHL on Polygon into time-locked claims on a destination chain, including wallet pairing, agreement recording and Merkle proofs.
Result
Deployed the public interface, Polygon swap and receipt contracts, and a funded BSC demo claim contract. Demo parameters: a ten-minute lock and TGIVE destination token.
My part
What I did
Each swap needs its own destination and unlock time. Multiple positions from the same wallet must remain independently claimable, even when their amounts and timestamps are identical.
01
Swap experience
Built the interface, Phil wallet pairing, position display and agreement-signing flow.
02
Position contracts
Implemented swap positions and locked receipts with a separate unlock time and destination for each position.
03
Destination claims
Implemented snapshot-based Merkle claims, duplicate-claim protection and deployment across Polygon and BSC.
How it worksSimplified walkthrough. No live transactions.
One swap, one position, one claim
Wallet + agreement registry
The wallet signs the acknowledgement and records the document hash before the swap. Personal information is not written as plain text on-chain.
Document hash + wallet signatureThe acknowledgement is tied to the wallet and document version.Example state, not live data
- Position
- Not created
- Unlock
- Not started
- Proof
- Not published
Polygon swap + receipt
The swap creates a position carrying its amount, destination chain and unlock time. The interface reads positions directly from the contract.
PositionOpened → positionsOfThe lock belongs to the position, not the whole wallet.Example state, not live data
- Position
- Created
- Unlock
- Time locked
- Proof
- Not published
Snapshot + destination contract
A snapshot becomes a Merkle root published to the destination claim contract by its administrator.
account + positionIndex + amount + unlockAtThe position index distinguishes otherwise identical positions.Example state, not live data
- Position
- Snapshotted
- Unlock
- Time locked
- Proof
- Published
BSC claim contract
After the position unlocks, the contract verifies its proof, marks the leaf as claimed and sends the destination tokens to the recipient.
MerkleProof → claimedLeaf → transferAn already-claimed leaf cannot pay a second time.Example state, not live data
- Position
- Claimed
- Unlock
- Time reached
- Proof
- Leaf consumed
Trade-offs
Decisions I made
Explicit trust boundary
The administrator publishes the snapshot root. This is a snapshot-based conversion system, not a trustless bridge.
Links and records
See the work
Live demonstrationOpen the GIVE Swap demo
Public demo interface. Inspect without connecting a wallet or making a transaction.
Based on contract source, deployment handoff and the publicly accessible demo. Contract and product links identify the implementation artifacts.
Demonstration configuration: ten-minute lock and TGIVE demo token on BSC. This is not represented as the final production rollout.