Testnet identities

The demo scripts sign transactions with named identities in the Stellar CLI’s keystore. They never read a secret key themselves, and they refuse to run against any network but testnet.

Create the identities

Each command creates a key, stores it in the keystore and funds the account from Friendbot, testnet’s faucet:

for k in assay-admin assay-issuer assay-attestor-a assay-attestor-b assay-witness assay-borrower; do
  stellar keys generate "$k" --network testnet --fund
done

Identity	Role in the demos	Used by
`assay-admin`	Deploys the contracts; registry admin	both demos
`assay-issuer`	Issues the demo asset `ADEMO`; asset admin in the registry	both demos
`assay-attestor-a`	Posts reserve reports	both demos, `sign-report`
`assay-attestor-b`	Second attestor	registry demo
`assay-witness`	Posts the on-chain supply	both demos
`assay-borrower`	Deposits collateral and borrows from the demo pool	circuit breaker

Check them

Print the public addresses (never the secrets):

stellar keys address assay-admin

A real run from 14 October 2026:

✅ Key saved with alias assay-newcomer in "~/.config/soroban/identity/assay-newcomer.toml"
✅ Account assay-newcomer funded on "Test SDF Network ; September 2015"
assay-admin        GDG23ZJYA4DPRZIWFMEKNDCMFZ2NGT56CM63D4JHU57W4FSOEN4QAGWN
assay-issuer       GDTB33U75MGMILME2RWXBL5CUPZP4W43Y225OLWUOZ7D2YNSBQTUOPKE
assay-attestor-a   GBQK5IGFFJUEMJJ6G4ZRU2N4ZBUUEV2OFYUQSEXLOI5NMV6FHJ6F7ZPC
…

If Friendbot is down

Funding can fail when Friendbot is busy. Re-run with an existing name: stellar keys fund assay-admin --network testnet.

Run the registry demo.