Vela devnet run by Synsema
A public instance of Horizen's Vela starter kit — Anvil, the Vela contracts, the subgraph, the Manager and an Executor with an emulated enclave — for anyone who wants to deploy a WASM app and watch it run without the nine containers on their own machine. Any module the starter kit runs: TinyGo, Rust, Synsema. Known keys, no attestation, reset from time to time: a place to iterate, not to keep value.
Applications
Requests to the enclave
Access
Get in
One call gives you a token and an account of your own — 10 000 ETH, DEPLOYER_ROLE and 100 000 TST — with the URLs that use it:
curl -X POST https://devnet.synsema.app/token
The answer carries env_text (the VELA_* lines a Synsema kit reads from .env; synsema run vela_client.syn -- devnet writes them for you), wallet_conf (a ready wallet.conf for Horizen's novaw) and the same values one by one for any other client. The devnet keeps your address, never your key. Ten tokens an hour per address.
Your URLs
- HTTP only: poll for receipts and completions (the kits and novaw do); there are no WebSocket subscriptions.
- The RPC serves the standard eth_/net_/web3_ read and send methods. The chain's own controls (anvil_*, evm_*, the unlocked accounts) stay on the machine, and a transaction signed by one of the chain's ten built-in accounts is refused: nobody can rewind the chain or act as its admin from outside.
- The chain's clock runs at real pace but behind the wall: durations are right, hours are not.
Allowlists
Two admin actions are yours, signed by the devnet: allowlist an ERC-20 of your own, and allow an auditor for an app your account deployed (deanonymization reports revert with AuthorityNotAllowed until then).
curl -X POST https://devnet.synsema.app/<token>/allow-token \
-H 'content-type: application/json' -d '{"address":"0x…"}'
curl -X POST https://devnet.synsema.app/<token>/allow-authority \
-H 'content-type: application/json' -d '{"app_id":"…","address":"0x…"}'
From a Synsema kit: vela_client.syn -- allow-token <address> and -- allow-authority <appId> <address>. The test token is already allowlisted. What you cannot test here: attestation (the kit's authenticator checks none) and production key management.
Recent activity
| What | App | Result | When |
|---|---|---|---|
| … | |||
Addresses
| Contract | Address | .env | wallet.conf |
|---|