Documentation

SmartLC is a programmable payment-guarantee protocol concept for Robinhood Chain. This build includes a working browser application and a deployment-ready architecture outline for the onchain escrow layer.

SmartLC protocol model

Traditional banking Letters of Credit place a bank or group of banks between an applicant and beneficiary. SmartLC is designed to replace the payment-control portion of that workflow with a Robinhood Chain smart contract that can hold supported digital assets and release them only under predefined conditions.

Important: SmartLC software is not a bank, does not currently issue bank-backed Letters of Credit, and does not guarantee the creditworthiness of a counterparty. A funded SmartLC would represent smart-contract-controlled digital assets, not a promise from an issuing bank.

Robinhood Chain network

SmartLC is configured for Robinhood Chain mainnet, an EVM-compatible Ethereum Layer 2. The web wallet flow can request the network automatically through standard EIP-1193 methods.

Network: Robinhood Chain
Chain ID: 4663
Gas token: ETH
RPC: https://rpc.mainnet.chain.robinhood.com
Explorer: https://robinhoodchain.blockscout.com

Core roles

Applicant

The party creating the SmartLC and committing the settlement asset.

Beneficiary

The wallet entitled to settlement if the conditions are satisfied.

Verifier or resolver

An optional party or mechanism that can attest to offchain conditions or resolve disputes. Production deployments should define authority, conflicts, appeals, and liability clearly.

SmartLC smart contract

The Robinhood Chain smart contract responsible for storing the LC state, controlling escrow accounts, validating authorized actions, and releasing or refunding assets.

Lifecycle

  1. Create terms including amount, asset, beneficiary, expiry, conditions, and resolution path.
  2. Fund the escrow controlled by the SmartLC smart contract.
  3. Record condition completion through wallet approvals, verifiers, or onchain logic.
  4. Settle to the beneficiary when the release rules are satisfied.
  5. Refund or resolve according to expiry and dispute rules when settlement conditions fail.

Settlement assets

The protocol is intended to support Robinhood Chain assets. For commercial transactions, stablecoins such as USDC may be preferable because they reduce the volatility mismatch between an invoice and its settlement asset. The production contract should use explicit token-contract allowlists or per-LC contract configuration rather than assuming all ERC-20 assets are equivalent.

Applicant wallet
    │
    │ create + fund
    ▼
SmartLC smart contract ─── stores terms / state
    │
    ├── escrow asset balance
    │
    ├── verifier / resolver rules
    │
    └── release or refund
             │
             ▼
       Beneficiary wallet

Application integration

The included website stores LCs in localStorage while onchain mode is disabled. This lets the full create, open, verify, dispute, and settle interface be tested without pretending that demo balances are real escrow.

To connect the application to a deployed smart contract, update config.js with the contract address and replace the prototype lifecycle calls in app.js with signed Robinhood Chain transactions. Wallet connection already supports injected EVM wallets such as Robinhood Wallet or MetaMask through the EIP-1193 browser provider interface.

Public token configuration

The public $SMARTLC contract address and external links are managed separately in config.json. Set the ca value once the official $SMARTLC contract is available. The website automatically updates every displayed contract address and builds all Pons Launchpad buy links from that CA.

Production deployment checklist

  • Implement and compile the Robinhood Chain smart contract with reviewed access controls, state transitions, and token-transfer checks.
  • Deploy to Robinhood Chain Testnet and run end-to-end tests with test assets.
  • Complete an independent smart-contract security review.
  • Configure the verified production contract address.
  • Choose supported token contracts and validate token addresses, balances, allowances, and transfer behavior.
  • Define resolver governance and emergency procedures.
  • Finalize legal terms, entity structure, sanctions/KYC policy where applicable, and jurisdictional availability.
  • Deploy mainnet only after the operational and legal controls match the intended product.

What this package does and does not do

The website is fully interactive as a prototype and can connect to an EVM wallet. It does not move real assets because no SmartLC mainnet contract or official $SMARTLC contract has been supplied. The package intentionally does not invent a live contract address, token contract, reserve balance, audit, bank relationship, or regulatory status.