Real testnet execution
Wallet signatures, USDC approvals, Community roles, votes, settlements, Treasury requests and validator rewards are sent to deployed Arc Testnet contracts.
Important
This is an active test environment.
BERT runs on Arc Testnet while we validate security, economics and UX before mainnet. Testnet USDC, ETH and every displayed testnet balance are for testing only. Do not treat them as redeemable assets or rely on the testnet for production activity.
Before you start
What is real, and what can change.
Testnet conditions
Deployments, settings, indexers and testnet balances can be reset or changed during development. Record transaction hashes when reporting unexpected behavior.
Demo PoP is required
Arc Testnet uses a clearly labelled Demo verification record before protected actions such as creating an idea or voting. It is not a human identity check.
Help harden BERT
If something behaves incorrectly, reproduce it on testnet first and report it privately. Do not exploit a weakness beyond the minimum proof needed to demonstrate impact.
Demo verification
Use protected testnet flows without an identity provider.
While BERT is on Arc Testnet, use Use demo verification in the dApp. It creates a test-only signed record for your connected wallet and then records it through the real deployed PoPVerifierUpgradeable contract.
- 1
Connect Arc Testnet
Connect the wallet that will create, join, vote or test another protected BERT flow.
- 2
Request Demo verification
Open Profile and press “Use demo verification”. No QR code, World App or simulator is needed.
- 3
Confirm on-chain
Approve the transaction in your wallet. BERT then records an active verification for this testnet address.
- 4
Use the dApp
Return to the intended action. You can now test the real contract checks, USDC approvals, votes and settlements.
Important: Demo verification proves nothing about a real person and must not be used to assess Sybil resistance, reputation or eligibility. On mainnet, Demo verification is disabled and BERT will require production World ID proof-of-personhood instead.
Testnet bug bounty
Help find the issue before mainnet.
BERT welcomes responsible reports for the open core contracts, V3 Community Layer, backend verification service and frontend integration. Public source code is intentional: security must survive review, not depend on hiding implementation details.
In scope
- Smart-contract access control, accounting, upgrade and state-machine flaws.
- V2/V3 business logic, Treasury, voting, settlement and reward defects.
- Backend proof validation and signature integration.
- Frontend defects that misrepresent on-chain state or enable an unsafe flow.
Out of scope
- Known, duplicate or purely theoretical reports without a reproduction.
- Social engineering, phishing, denial of service, spam or third-party service issues.
- Testnet token value claims and reports that require harming other users.
- Reports containing copied secrets, personal data or public exploit details.
Reward: an initial Validator seat
For a confirmed, previously unknown and responsibly disclosed high-impact report before mainnet launch, BERT may include the researcher's wallet in initialValidators when the official BERT Community is deployed. It is not an immediate cash payment or transferable asset, and remains subject to available seats and conduct requirements. After the Community is live, new Validators must follow the standard on-chain eligibility path.
Private disclosure only
Send a reproducible report.
Use a GitHub Private Security Advisory. Include the affected repository and component, preconditions, exact reproduction steps, expected and actual behavior, impact, transaction hashes or screenshots, and a proposed mitigation if you have one.