Reputation Points Aggregation Bridge by 3327
Aztec Grant Proposal
Contact Details
Vladan Andric
Signal: Albee.42
vladan.andric@mvpworkshop.co
Summary
The 3327 Points Bridge enables users to privately manage and attest to scores and reputation across apps and chains. Whether it’s game levels, loyalty points, or governance reputation, users store their data privately on Aztec L2, and bridge attestations to other EVM chains using a custom decentralized bridge.
Each user has a unique, app-specific ID, ensuring privacy and preventing correlation between apps. We provide a Point Score dApp (browser extension) for users and a Web SDK for apps to integrate attestation verification seamlessly.
This proposal expands upon value propositions that emerged during our previous work developing a single-chain reputation system see demo. That project highlighted a critical limitation: existing solutions are siloed per chain, making it difficult to build a cohesive user experience across the multi-chain Web3 landscape. Aztec’s privacy-preserving infrastructure is the ideal foundation to fix that.
Timeline
Start Date: April 1, 2025
End Date: June 28, 2025
About Us
3327 R&D is the cryptographic research and development unit of MVP Workshop, with deep experience in ZKPs, decentralized systems, and privacy-focused infrastructure. Our past work includes:
ZKSim - a zero-knowledge circuit simulator for VS Code and full desktop IDE (in development)
Multiple grants from the Ethereum Foundation (ie., post-quantum stealth address protocol, MACI improvements, etc.)
Active contributions to Noir, Circom, and Ethereum tooling ie. Noir language library for floating point numbers
Curvy Protocol - Elliptic Curve Pairing Stealth Address Protocol that allows both individuals/businesses to receive funds anonymously by generating unique, one-time-use stealth addresses for every transaction.
Makers of Polygon Edge
Internally developed EVM/UTxO wallet
A multidisciplinary team with backgrounds in academic cryptography (2 PhDs in Mathematics and Cryptography), smart contracts, and Web3 UX, dapps, blockchain infrastructure.
Project Details
We will build a fully functioning cross-chain score and reputation system consisting of:
- Point Score dApp - browser extension for user profile management
Bridge Contracts - deployed on Aztec and Optimism testnet- Profile Contracts - for private score storage on Aztec
Web SDK - for applications to request/verify attestations- Bridge Infrastructure - starting centralized, with a roadmap to decentralization
Bridging mechanism
The bridge will have a decentralized set of validators and relays coordinated via bridge contracts. The bridge contract on the Aztec chain collects requests for registrations, attestation, and points aggregation from the profile contract, with guarantees that the attestations and registrations are valid. The attestations are batched and each batch is signed by the validators using BLS signatures. The relay aggregates a BLS threshold signature and submits the batch, along with the signature, to the L2 smart contract where the attestations are published. Each batch will have a designated nonce to prevent duplicate submissions.
The point aggregation requests are individually stored and the relay summarizes all the collected point updates on the L2 smart contract and publishes a batch of aggregated scores to the Aztec chain. The validators confirm the batch validity and after a threshold number of validators have confirmed all point updates in the batch the users can claim their aggregated points updates and update their private profile storage. As the users are only updating the state with the received values without any mathematical operations, there are no issues of double-spending nature.
In the PoC version, two validators and one relay will play the role of the bridge operators in a centralized manner, while the production version will introduce methods for each validator to participate as a relay for batches and receive fee rewards for the successfully published batch.
Challenges and edge cases
The main challenge for the bridge is assuring that the time required for bridging is short enough for the benefits of the UX while being long enough to ensure the chain reorgs will not happen on L1 or L2s. The specific use case for the bridge does not have critical requirements for high-speed executions and no possibility of double spending, so the waiting time on L1 can be limited to soft block finality. As soon as the attestation is confirmed to the L2 chain, the user can submit the attestation to the application, while the applications that require attestation can decide on the waiting period until the attestation with a given ID can be considered valid. Additionally, by design, all user points are non-transferable. In the future, if rewards are introduced based on user reputation, these points would act solely as a qualification mechanism, not as a tradable asset.
The point aggregation flow will not add significant waiting time as the user requests for aggregation will be asynchronous from the point updating transactions on the L2 chain. The point update transactions will be initiated by the applications using the point system while users will request the point aggregation in arbitrary time periods, expected to be later than the point update time plus the reasonable time for waiting for the required number of block confirmations.
The Attestation relaying time may be controlled by reducing the batch size and batch timeout on-demand, thus reducing the waiting time for the batch to be signed and transmitted.
One of the challenges that we think we solved by design is how to prevent the double spending problem.
User Flow Diagram [link]
Sequence Diagram [link]
Deliverables & Milestones
[grant] Milestone 1: Core Infrastructure Setup (by May 1, 2025)
- UI/UX for Point Score dApp
Wireframes and interface design for registration, point tracking, attestation creation. - Bridge Contracts v1
Smart contracts on Aztec and Optimism for relaying registration, update, and attestation data. - Two validators - one relay bridge
Centralized bridge infrastructure to demonstrate PoC message passing.
[grant] Milestone 2: POC on Testnet (by June 1, 2025)
- Profile Contracts
Privacy-preserving contracts on Aztec for storing scores, IDs, and user logic. - Basic Web SDK
SDK for dApps to integrate registration, update requests, and verify attestations. - Point Score dApp Alpha
A working browser extension for private user interaction with scores and claims. - Deployed PoC System
Full deployment to Aztec & Optimism testnets.
[grant] Milestone 3: PoC Testing and Demo (by June 28, 2025)
- Demo Applications Tested
At least 2 apps (ie. a game and rewards dApp) issuing/verifying scores via the bridge. - Documentation
- Recording Tutorial Videos and Promotion
Internal Milestones
[internal] Milestone 1: Bridge Decentralization (by July 31, 2025)
- Multi-Node Bridge network
Extend the relay to support multiple validators and relays for higher trust minimization. - Validator Mechanism
Basic interface or CLI for node registration/election.
[internal] Milestone 2: Finalization and Launch (by August 31, 2025)
- Robust Test Suite
End-to-end testing, unit, and integration coverage. - Mainnet Launch
Audited, deployed, and open-sourced Point Bridge on Aztec and selected EVM L2.
Future Work
- Integration with other L2s (Arbitrum, Base, Scroll)
- Complex ZK attestation logic using Noir
- Full public release of SDK + dApp tooling
- Social UX components for point-based interactions
Grant Amount Requested
$45,000 USD
Budget Rationale
The requested budget of $45,000 will be used to support a cross-functional development team throughout the 3-month project timeline. Our team brings together expertise across:
- Product & UX Design - for building a seamless and intuitive browser extension experience.
- Smart Contract Engineering - to implement secure and verifiable bridge and profile contracts across Aztec and Optimism.
- Cryptography Research - to design robust attestation logic and validator coordination using threshold signatures.
- Frontend & Backend Development - to deliver the Point Score dApp, Web SDK, and supporting infrastructure.
- Project Management & QA - to ensure timely delivery, testing coverage, and alignment with Aztec’s best practices.
This budget will also cover internal costs for running the PoC infrastructure (validators and relays), demo app development, documentation, and testing environments.
| Category | Description of the efforts needed |
|---|---|
| DApp Design & Dev | UI design, extension integration, UX testing |
| Bridge Contract Dev | Aztec & L2 bridge contracts, event management |
| Web SDK | Developer integration for attestation requests |
| Profile Contract Dev | Private ID + score logic on Aztec |
| Demo Apps | Game + loyalty demo for showcasing end-to-end UX |
| Bridge validator and relay nodes | Centralized PoC + bootstrapping multi-node validator and relay architecture |
| Testing & Documentation | Test suite, guides, walkthroughs |
Questions for the Aztec Team
- Are there recommended Noir design patterns for implementing threshold attestations (ie. score > N)?
- Would it be helpful to include a future integration plan with Aztec Connect or other core infra?
Thanks for considering our proposal! We’re excited to help unify privacy, reputation, and interoperability on Aztec.