Feature/update payment#17
Merged
Merged
Conversation
…from create_round API - Replace dynamic circuit selection with a single fixed circuit (9-4-3-125 prod, 2-1-1-5 for test-circuit feature); circuit params now returned by get_maci_parameters() - Remove max_voter from ExecuteMsg::CreateRound (registry) and CreateAmaciRound (api-saas); capacity enforcement is delegated to the amaci contract at signup/add_new_key time - Add fee and delay query endpoints to amaci contract (get_message_fee, get_signup_fee, get_deactivate_fee, get_base_delay, get_message_delay, get_signup_delay, get_deactivate_delay) - Add registry migrate_v0_1_6 and api-saas migration; update state and schema accordingly - Sync TypeScript SDK clients and types to reflect API changes - Remove stale circuit progress/fix markdown files from packages/circuits
…tibility Introduce ROUND_FEE_CONFIG (Map<round_addr, RoundFeeConfig>) to capture signup/message/deactivate fees at round creation time via registry events. All proxy operations now look up the fee from this map instead of the global SAAS_FEE_CONFIG, ensuring correct fee accounting across rounds created under different fee regimes. Backward compatibility: rounds with no entry fall back to legacy defaults (signup_fee=0, message_fee=0.06 DORA, deactivate_fee=10 DORA). SaasFeeConfig is simplified to base_fee only, as the other three fees are now managed per-round.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…key_unauthorized test_saas_full_round_signup_addnewkey_tally
…nsactions - Replace single rpcEndpoint/restEndpoint with rpcEndpoints[]/restEndpoints[] arrays - Wrap every contract write method in withRetry (primary-first rotation, fixed 200ms delay, 5 retries) - Decouple broadcast from confirmation: use signAndBroadcastSync + waitForTransaction - Add direct-path methods to Contract class (signup, addNewKey, publishMessage, publishDeactivateMessage, preAddNewKey, claim, executeWithRetry) to ensure retry coverage on all non-SAAS code paths - Unify all maci.ts raw*/high-level methods to route through contract.ts retry wrappers - Fast-fail on BroadcastTxError (mempool rejection); fast-fail on 4xx HTTP errors in fetchRest - Add per-retry console.warn logs for both RPC and REST failures - Add path-selection logs ([rawSignup], [rawDeactivate], etc.) to trace SAAS vs direct routing
…oint defaults
- Migrate default apiEndpoint to maci-graphql.dorafactory.org (mainnet) and maci-testnet-graphql.dorafactory.org (testnet)
- Replace NetworkConfig.rpcEndpoint/restEndpoint with rpcEndpoints[]/restEndpoints[] arrays; mainnet defaults to primary + archive endpoints
- Update RoundType: operator(string) → operatorAddress, identity → operator{identity}
- Update OperatorDelayType: remove nodeId, roundAddress → contractAddress
- Update DeactivateMessage: maciContractAddress → contractAddress, maciOperator → operatorAddress
- Update all GraphQL queries in round.ts / operator.ts / event.ts to match new schema
- Add test framework: unit tests (http/retry), integration tests (all 22 query methods, fully automated)
- Add sdk-tests job to CI workflow
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.