Suggested area: Rust, TypeScript, Deployment
Summary
The contract exists in contracts/anonvote/src/lib.rs and the deploy
steps are documented in the README but the contract has never actually
been deployed. There is no contract ID recorded anywhere in the repo.
sorobanService.ts references a SOROBAN_CONTRACT_ID environment
variable that has no default value and no working testnet ID to test
against. Any contributor trying to wire sorobanService.ts into core
hits a blank env var immediately.
Scope
- Build the contract WASM —
cargo build --target wasm32-unknown-unknown --release
and confirm it compiles cleanly with no warnings
- Deploy to Stellar testnet using the
stellar contract deploy command
documented in the README
- Run
initialize with an AnonVote testnet admin public key
- Record the deployed contract ID in a
DEPLOYMENTS.md file at the repo
root — include network, contract ID, admin address, and deploy date
- Add the testnet contract ID as the default value in
service/.env.example
so contributors can run sorobanService.ts against a real deployed
contract without manual setup
- Confirm
cargo test passes against the deployed contract ID
Relevant files
contracts/anonvote/src/lib.rs
service/sorobanService.ts
README.md
Acceptance Criteria
Out of scope
- Mainnet deployment
- Changes to contract logic or function signatures
Suggested area: Rust, TypeScript, Deployment
Summary
The contract exists in
contracts/anonvote/src/lib.rsand the deploysteps are documented in the README but the contract has never actually
been deployed. There is no contract ID recorded anywhere in the repo.
sorobanService.tsreferences aSOROBAN_CONTRACT_IDenvironmentvariable that has no default value and no working testnet ID to test
against. Any contributor trying to wire
sorobanService.tsinto corehits a blank env var immediately.
Scope
cargo build --target wasm32-unknown-unknown --releaseand confirm it compiles cleanly with no warnings
stellar contract deploycommanddocumented in the README
initializewith an AnonVote testnet admin public keyDEPLOYMENTS.mdfile at the reporoot — include network, contract ID, admin address, and deploy date
service/.env.exampleso contributors can run
sorobanService.tsagainst a real deployedcontract without manual setup
cargo testpasses against the deployed contract IDRelevant files
contracts/anonvote/src/lib.rsservice/sorobanService.tsREADME.mdAcceptance Criteria
DEPLOYMENTS.mdwith network, adminaddress, and deploy date
service/.env.examplecontains the testnet contract ID as a defaultcargo testpasses against the deployed instanceany step that does not
Out of scope