01 / Send USDC

Loading network…

Receiving address

Unavailable

Suggested contribution: multiples of 100 USDC.

Official USDC contract · 6 decimalsUnavailable

Use a wallet you control. Do not withdraw from an exchange or smart contract to this address; ownership may be unverifiable.

Keep this wallet and its sending address for final SI wallet confirmation. Ethereum mainnet USDC only. Never share keys or seed phrases.

02 / Verify & email

One hash, one receipt

Each hash is recorded once. Save your code; it will not appear again.

Checking availability…

Receipt verification does not establish payment ownership or allocation. Read the terms ↓

USDC on Ethereum · No wallet connectionFunding terms & allocation

FUNDING / DETAILS

Before you contribute.

dev@siworld.io ↗

01 / Supporter allocation

Up to 4% of block rewards comes from the existing 10% development fund: 90% miners / at least 6% development / up to 4% supporters.

Up to 4% × your accepted USDC ÷ all accepted USDC

Refunds do not count. Includes testnet tokens and separate future mainnet SI rights, intended long term after launch. Testnet tokens have no value, may reset and do not convert into mainnet balances. Mainnet launch, token value and returns are not guaranteed.

02 / Deadline & refunds

20,000 USDC soft target · 40,000 USDC hard cap. Missing the soft target does not trigger refunds. Reaching it in verified submitted receipts starts one saved 24-hour window; expiry closes hash submissions.

Excess and later receipts are to be refunded after manual reconciliation and ownership review. Limits count 1 USDC as $1. The page cannot stop Ethereum transfers; email support about late payments.

03 / Confirm your wallet

Each hash records once. Codes do not prove ownership; copied hashes and lost codes need manual email review. Keep your sending wallet and address for final confirmation.

A one-time signed message may be requested. Never provide keys, seed phrases or another payment. Email your code to dev@siworld.io; watch for a reply requesting your SI address.

04 / Fund use & privacy

Supports node engineering, reliability and security. Planned GitHub reports cover aggregate receipts, refunds, spending and progress.

The bar shows verified submitted receipts before refunds, not all receipts or final accepted funds. Email, codes and SI addresses stay private. Publishing names, amounts or transaction references requires separate consent.