Agapao is a network whose currency, AGAPE, funds beneficial causes as it runs. Part of the new currency goes to a public treasury, in a share each validator chooses, and the people who stake AGAPE choose the vetted causes it pays.
Otherwise it works as digital money should: yours to control, final in seconds, and private when you choose.
Devnet Agapao runs today as a public test network. Its coins have no value, it can be reset at any time, and there's no mainnet yet.
How giving works
Nobody has to remember to donate. Giving is part of the ledger itself, the same code that moves every payment, and it runs in four steps.
Every block creates new AGAPE. The validator that proposed it sends its chosen percentage of that, anywhere from 0 to 100, to the treasury.
Philanthropic Service Providers bond 100,000 AGAPE and vouch on chain for the beneficial causes they've checked: registered recipients with a name, documents and withdrawal addresses. Anyone can then group up to eight vetted causes into a slate.
Everyone with stake can point a standing vote at one slate, weighted by their stake. The vote stays where it is until they move it.
The treasury divides its whole balance among slates by their votes, and each slate's part is split equally among its causes that are still vetted.
Blocks create 21,024,000 AGAPE a year at first, halving about every 2.4 years until it settles at 1,314,000 a year for good. What a validator doesn't send to the treasury goes to it and the people staked with it.
The treasury also receives the base fee of every transaction, the 500 AGAPE fee every new validator pays, the 100 AGAPE deposit for each slate, the 1,000 AGAPE fee for creating an asset, all the stake validators lose as penalties (for signing two conflicting blocks, or for a day offline), and most of what a PSP loses when a challenge against its vetting is upheld.
Anyone can skip the treasury and give to a vetted beneficial cause straight from their wallet. A private donor moves the amount to their public balance first, and the wallet does both steps as one.
Every validator's percentage, every vote, every attestation and every payout is on the public ledger, so anyone can check the rules were followed. Your own payments can be private. The giving can't be.
Nobody is in charge of it. There's no foundation, admin key or privileged address in the ledger. Validators set their own percentages, stake holders choose the slates, and PSPs decide which causes they vouch for.
Everyone here takes part in the same network, and that network funds beneficial causes. Anyone can take any of these parts, and one account can take several. None of them needs anyone's permission, only the stake or bond some of them call for.
A beneficial cause registers on chain, gets vetted by a Philanthropic Service Provider, then receives donations and a share of the treasury every 30 days.
More about beneficial causesBond 100,000 AGAPE, check beneficial causes by your own published standards, and vouch for the ones that pass. Every attestation is public.
More about philanthropic service providersValidators run the network, and each one decides what share of the new AGAPE in its blocks goes to beneficial causes. Delegators choose which validators to back.
More about validators and delegatorsHold AGAPE in a wallet that keeps its keys on your own device. Send it in seconds, privately when you choose, and give to vetted beneficial causes from the same place.
More about savers and giversTake payments that are final in about 2 seconds, for a fee that depends on a payment's size in bytes and not on its amount.
More about people doing businessDeploy small programs that hold AGAPE and can give to vetted beneficial causes. People use them from the wallet, with no app of your own to build.
More about buildersBeneficial causes
Donations sent straight to the cause, and a share of the treasury every 30 days when stake holders vote for a slate the cause is on.
A public record of everything the cause has received, which any donor can check.
Anyone can register a beneficial cause: a record on chain with a name, a link to its documents and up to four withdrawal addresses. A Philanthropic Service Provider (PSP) then checks the cause and vouches for it on chain, and the cause names that PSP as the one it pays for vetting. Until it has one, the cause can't receive donations or payouts.
Money arrives in the cause's balance on chain, and one of its withdrawal addresses takes it out.
To turn AGAPE into local currency, a cause sells its own AGAPE through a licensed exchange, broker or crypto-donation processor, which handles the identity checks for that sale. That needs AGAPE to be tradeable somewhere the cause can reach, and with no mainnet yet, it isn't. Until then a cause holds what it receives.
Live on the devnet Registration, vetting, donations in AGAPE and other assets, and payouts.
Not yet Decided, not built: a newly vetted cause waits 30 days before the treasury pays it, and a payout pays at most a sixth of the treasury.
Philanthropic Service Providers
A public record of every beneficial cause you've vouched for, tied to your bond, which voters see when they choose what to fund.
A fee for vetting, which you set at up to 3% of what each cause that names you receives. It can be withdrawn 21 days after the end of the day the cause receives the money.
Your own standards and your own services. You can sell causes other work (e.g. tax receipts or reporting) on terms you agree with them.
Bond at least 100,000 AGAPE, check causes off chain (e.g. their legal registration, their control of their withdrawal addresses, sanctions screening), and attest to the ones that pass. Revoke an attestation when a cause stops passing.
A PSP never holds or converts a cause's money. Payouts and donations go only to the cause's own addresses.
Register and bond
Your bond of at least 100,000 AGAPE moves into escrow on your PSP record, with your name and a link to your methods.
Check the cause
Off chain, by the standards you publish.
Attest on chain
The cause shows as vetted by you, and can be put on a slate and receive donations and payouts.
Keep watching
If the cause stops passing, revoke the attestation. If it changes its withdrawal addresses, the ledger clears every attestation until a PSP checks it again.
Live on the devnet Bonds and attestations, a vetting fee of at most 3% of what a cause receives, paid to the PSP the cause chooses, and public challenges that cost a PSP part of its bond if a cause it vouched for shouldn't have been vetted.
Not yet Decided, not built: the treasury pays on a new PSP's vetting only after its bond has stood for 90 days.
Validators and delegators
A say in how much the network gives. Each validator sets a philanthropy percentage, from 0 to 100, and that share of the new AGAPE in every block it proposes goes to the treasury.
Rewards for securing the network. Each validator publishes two rates on chain: its philanthropy percentage and its commission. When it proposes a block, the block's new AGAPE is split by formula: the philanthropy percentage goes to the treasury, the commission is taken from what's left, and the remainder is shared by everyone staked with the validator, in proportion to their stake. With 40% philanthropy and 5% commission, 100 new AGAPE becomes 40 for the treasury, 3 for the validator and 57 shared by stake.
Holders who don't run a node can delegate their stake to a validator, and in choosing one they choose its philanthropy percentage. The wallet lists validators by that percentage first, and delegators claim their share from it.
Run a node, and register with at least 10,000 AGAPE of your own stake. Every hour, the 100 validators with the most stake form the set that proposes and votes on blocks.
Stay online and sign honestly. Signing two conflicting blocks costs a validator 5% of its stake and its place for good.
Live on the devnet Staking, delegation, the hourly validator set, the 5% cap on any validator's voting power, and slashing.
Savers and givers
A wallet for desktop computers and Android phones. Your keys never leave the device, and the wallet is locked with a password or, on Android, with the phone's fingerprint or screen lock.
Two balances. The public one works like a bank statement anyone can read. The private one hides the sender, the recipient and the amount of every payment made inside it, and you decide, payment by payment, which one to use.
You write down a 24-word recovery phrase once, then send and receive with addresses or QR codes.
Before anything is signed, the wallet shows what's in the transaction, written from the exact bytes it's about to sign. You can give to any vetted beneficial cause from either balance.
You can also delegate stake to a validator, which gives you a vote on which causes the treasury funds. Validators and delegators, below, says how that works and what it risks.
Live on the devnet The wallet app, on desktop computers and Android. The Android app is on the releases page.
Not yet Signed desktop builds, and a listing on Google Play. For now the desktop app is built from source.
People doing business
Payments that can't be reversed once their block is decided, which happens about every 2 seconds. There's nothing to wait for after that.
Fees that don't grow with the amount. A transaction pays for its size in bytes, so paying a supplier a large sum costs the same as a small one.
Give a customer an address or a QR code, and keep separate addresses for separate purposes (e.g. one for sales and one for paying suppliers). Each address has its own balance and history.
A shop can also give part of every sale to a beneficial cause automatically, with a contract (see Builders).
Your customer pays
They send AGAPE to your address, scanned from a QR code or pasted in.
The next block carries it
Blocks come about every 2 seconds, so the payment is in one within seconds of being sent.
It's final
Once validators holding more than two thirds of the stake sign the block, it's decided, and the payment can't be undone.
Live on the devnet Payments, fees and addresses, as described here.
Live on the devnet Other assets on the same ledger, so a business could price and settle in a stablecoin once a regulated issuer offers one.
Builders
Contracts: programs anyone can deploy that hold AGAPE, keep their own records and can donate to vetted beneficial causes. They make room for things like a shared giving fund that members pay into, with rules for who can withdraw and how much; escrow that releases a payment when both sides agree; a shop that sends part of every sale to a cause; or a cause's own rules for how it spends.
No app to build for your users. Each contract carries a description of its methods, and the wallet turns that into forms, shows what a call will do before it's signed, and decodes the contract's history.
Write a contract in Rust with the Agapao SDK and deploy it with the command-line tool. Its code can't be changed once deployed, so the rules people read are the rules that run.
Live on the devnet Contracts, from the first block, including contracts that hold assets and their mint and freeze powers, and that check other chains' proofs.
Not yet In development: a bridge to Ethereum, in a project of its own, built on these proof checks and asset powers.
What works today
The first list works on the public devnet now. The second is still to come, and none of it has a date.
A payment is final once its block is decided, about 2 seconds after you send it. Nobody can reverse it, so check the address before you confirm.
The wallet keeps your keys on your device, and your 24-word recovery phrase is the only other way back in. There's no account to reset: lose both, and nobody can get the money back for you.
It's a test network. Its coins have no value, and it can be reset at any time, which wipes every balance on it.
Payments are public unless you make them from your private balance. Moving money into or out of the private balance shows the amount and the public address on the other side.
Try the devnet
The devnet is a test network. Its coins have no value, and it may be reset at any time. A new wallet starts empty: the faucet sends 1,000 devnet AGAPE a day to a public devnet address. A validator's 10,000 AGAPE self-stake is more than the faucet sends; ask in the Matrix room for that.
Get devnet coinsagape-node is the node and a command-line wallet. On Linux, this installs the latest
release once it has checked the release's signature (it needs cosign 2.6 or
later):
curl -sSL https://agape.money/install.sh | sh Each release has builds for Linux (x86_64 and ARM64) and Windows, with checksums, signatures and a list of what's built into them. There's no macOS build yet.
Releases on GitLabEach release has the Android app as a universal APK, with its checksum, which installs on
Android 9 or later. It isn't on Google Play yet. The desktop app has no downloads yet, and
builds from source on macOS, Windows and Linux with Rust's cargo:
cargo run --release -p agape-wallet The source repository isn't public yet, so for now building it is for people who have a
copy. A new wallet connects to the devnet through https://agape.money/api, and
its Receive screen has a button that asks the faucet for coins.
The devnet's nodes answer at https://agape.money/api: balances, blocks,
validators, beneficial causes, slates and the treasury. The API explorer lists every request and lets
you send them from the browser.