✅ Sandbox Execution Verifier (SEV)

The Sandbox DAO Grant Program OPEN: Web3 integration
1

1. Executive Summary

The Sandbox Execution Verifier (SEV) will be an open-source tool designed to empower any community member to confirm that off-chain decisions approved by the DAO have been executed on-chain exactly as specified. By converting human-readable instructions into machine-verified proofs, SEV enhances transparency, reduces manual reconciliation errors, and builds collective trust in funded initiatives.

2. Problem Statement

Limitation/Gaps Identified:

  • Execution uncertainty: Many DAO-funded initiatives (e.g., NFT market-making, LP incentive campaigns, token grants, brand partnerships, community event payouts, and ad hoc airdrops) depend on off-chain instructions published in CSV/JSON files. Currently, there is no standardized, self-service way for participants to verify that these instructions were actually carried out on-chain as approved.**

Affected Parties:

  • Creators & Operators: Those tasked with executing off-chain strategies must manually reconcile results and report back, increasing operational overhead.
  • Community Members & Delegates: Holders, delegates, and observers cannot independently confirm execution accuracy, forcing them to trust manual reports or hidden scripts.
  • DAO Governance: Lack of verifiable proof can erode confidence in funded initiatives and slow decision-making.

Consequences if Unaddressed:

  • Increased Manual Effort & Errors: Reliance on spreadsheets or ad hoc scripts leads to miscalculations and delayed reconciliations.
  • Erosion of Trust: Community members may doubt that approved plans are followed accurately, hindering future participation.
  • Operational Friction: Creators and operators spend excessive time re-verifying results rather than focusing on strategic tasks.

3. Proposed Solution

Solution Overview: SEV is a modular, plugin-based verification platform consisting of a TypeScript core engine and React front-end. It performs two primary functions:

  1. File Integrity Check: Validate that the CSV/JSON instructions (hash stored on-chain) remain unaltered.
  2. Transaction Alignment Check: Compare approved parameters against actual on-chain events for the chosen use case (e.g., order counts and price ranges) and display a green :check_mark: or red ✗ result.

Underlying Technologies:

  • TypeScript Engine: Hashing, parsing, and compare logic for CSV/JSON vs. on-chain data.
  • React Front-End: Simple UI to paste a proposal link or CID and run the check.
  • Data Sources: IPFS/S3 for instructions; The Graph or RPC for on-chain events; Gnosis Safe API for multisig history.

Why This Solution:

  • Accuracy & Efficiency: Automates heavy reconciliation tasks, ensuring consistency between approved instructions and on-chain outcomes.
  • Accessibility: No wallet or blockchain knowledge required to verify; accessible to creators, delegates, and community observers.
  • Modularity & Extensibility: Plugin architecture allows adding future verification modules (treasury, grants, airdrops) with minimal overhead.

4. Team

Team/Studio: WakeUp Labs

Name Role Relevant Experience
Axel Product Designer UX/UI design for blockchain dApps, wireframing complex workflows, Figma expertise
Milton Technical Lead Architecting decentralized applications, smart contract development, backend integration
Nahuel Senior Full-Stack Developer 5+ years Web3 dev, React/TypeScript, Solidity, backend APIs, Executing test plans
Milestone Key Deliverable Estimated Completion (from approval)
— — —
M1: Analysis & Wireframes Case selection, data schema, wireframes for core workflow 1 week
M2: Development Build Execution Verifier engine and React UI; simulation mode 2 weeks
M3: QA & Deployment Testing, security review, production deployment, docs published 1 week

Web3 Portfolio & Credentials:

5. Technical Details

  • Core architecture:
    • TypeScript engine for computing hashes and comparing parameters.
    • React frontend for verification status and full user-flow processing.
    • Optional: IPFS integration for file hosting.
  • Data inputs:
    • Public CSV/JSON files (e.g., hosted on S3 or IPFS).
    • Transaction history via Gnosis Safe links. (Optional)
    • On-chain events from Etherscan or The Graph. (Optional)
  • Verification flow:
    • User publishes off-chain instructions in private CSV/JSON and records the file’s hash on-chain.
    • Executor carries out transactions manually.
    • User reveals the original CSV/JSON and the list of executed transactions.
    • SEV fetches the on-chain proof, recomputes the file hash, and compares parameters (counts, amounts, addresses) against actual tx data, displaying a green :check_mark: or red ✗ result.
  • Deployment:
    • Static website + AWS Lambda; MIT-licensed, open-source from day one.

6. Budget & Work Plan

Total Budget: 13,000 USDC

Milestone Key Deliverable Estimated Completion (from approval) % Budget Released
M1: Analysis & Wireframes Case selection, data schema, wireframes for core workflow 1 week 40% (5,200 USDC)
M2: Development Build Execution Verifier engine and React UI; simulation mode 2 weeks 30% (3,900 USDC)
M3: QA & Deployment Testing, security review, production deployment, docs published 1 week 30% (3,900 USDC)

7. DAO Alignment & Impact Measurement

Community Empowerment & Decentralization:

  • SEV shifts verification power from a small ops team to every community member, promoting inclusive oversight and reducing reliance on centralized actors.

Improved Creator & Player Experience:

  • Creators can focus on delivering initiatives rather than manual reconciliation; community members gain confidence in funded events, leading to higher participation.

Interoperability & Innovation:

  • SEV’s plugin-based core encourages custom verification modules (e.g., treasury, grant milestones) that can interoperate with other Sandbox DAO tools and subgraphs.

Impact Tracking & KPIs:

  • Verification Usage: Number of running verifications within 60 days.
  • Community Engagement: Feedback activity (forum posts, social mentions) quantifying trust improvements.
  • Time Saved: Reduction in manual reconciliation hours per funded initiative (tracked via pre- and post-launch surveys).

8. Attachments

2 Likes
2

Hello Wakeup Labs Team,

It’s a very interesting proposal, unfortunately it’s beyond the budget that can be approved by the Grant Program, which is a maximum of 50k sand , or about 13k USD.

3

Thank you for the response, @yuelwolf.

Is there any possibility to extend the budget?

In the meantime, we will do our best to reduce the scope while keeping the project functional and valuable for the ecosystem, and to adjust it as much as possible to the proposed limits. We would love to share the updated proposal next week.

4

Hello WakeUpLabs team,

Unfortunately it is not possible, for this kind of budget the indicate way is create a sip.

Sure, feel free to adjust the scope of the project if you consider that could be viable with the budget available of the Grant Program.

5

Hello Yuelwolf,

We’ve updated the proposal, adjusting the scope to align with the available budget from the Grant Program.

Let us know if you have any feedback or require further details.

1 Like
6

Thank you guys, the proposal is under review I will come back ASAP.

1 Like
8

Proposal Evaluation

Thank you for your time and effort in presenting this proposal @WakeUpLabs . Following a review based on the established criteria, here are the results:

Team (8/10 | Weight: 35%)

The WakeUp Labs team is well-structured with clearly defined key roles, demonstrating their capability to execute the proposal effectively.

Project (9/10 | Weight: 35%)

The Sandbox Execution Verifier (SEV) proposal is highly relevant and logical, addressing the critical need for transparency and trust in DAO governance.

Budget (7/10 | Weight: 15%)

The proposed budget of 50,000 SAND is reasonable for the development of such an important tool and falls within the permitted range.

DAO Impact (9/10 | Weight: 15%)

The project has a very positive impact for the DAO by supporting transparency and offering a tool for effectively tracking the execution of approved projects.

Compiled Score

The total weighted score for your proposal is 8.45.

Conclusion

The project has been approved. Congratulations! FYI @Geraldine @Paul

1 Like
9

Could you convert the budget you need in USDC as payment is made in USDC?

cc @yuelwolf for budget validation

2 Likes
10

Hi Geraldine,

Done!

1 Like
11

Kickoff & Milestone #1 | Sandbox Execution Verifier (SEV)

Hi DAO members! :waving_hand:

We recently kicked off the project with a joint alignment session to clarify goals, roles, and timelines. Now, just a few days later, we’re happy to share that Milestone #1 is complete and ready. This first phase focused on research and wireframes: working closely with Juan Pablo from the SandboxDAO, Axel, our Product Designer Strategist, and Miki, as Product Manager, we are starting to transform the DAO community’s pain points into concrete, testable flows that set the stage for development.

Deliverables

What we’ve built

  • Co-design workshops and pain-point mapping with Juan Pablo (SandboxDAO), Axel (Product Design Strategist) and Miki (Product Manager).

  • Detailed wireframes for upload file → validate hash → view result, tailored for Admin, Consultant and DAO Member roles.

  • Initial data schema that standardizes CSV/JSON files across DAO transactions (liquidation, authorization, acquisition, arbitrage, vault) and lays the rails for future automations.

Why are we not including the per-transaction “✓ / ✗” verifier?

The original roadmap included an automatic Transaction Alignment Check. After technical validation and several meetings, we agreed not to include it. In short:

  1. Diverse transactions. One engine would be fragile across all types of them.

  2. Spreadsheet vs. on-chain mismatch - we can’t reliably pair Excel rows with hashes (e.g., OpenSea sales). As Axel put it: “We can’t contrast Excel values with transaction hashes, so we provide approved instructions with their hash plus execution proofs.”

  3. Early value over complexity - a lightweight verifier today gives immediate transparency and lets us understand this as a progressive product that can go deeper in the future.

Refined scope

  • Task integrity check - verify that the approved file (on-chain hash) hasn’t been altered and was executed exactly as proposed.

  • Execution evidence - surface original instructions + on-chain hash + executed transactions so anyone in the DAO can run spot checks.

  • Growing with the DAO’s needs — add specialized modules (liquidations, authorizations, acquisition, vault, arbitrage) one by one as priorities emerge.

  • Foundations for scale - roles, back office and a DAO control center that evolve with the community.

What’s next (Milestone #2)

  • Build the Execution Verifier engine and a React UI in simulation mode.

  • Development kickoff - coding starts later this week (or early next), so you’ll see commits landing soon.

Thank you for the trust and the energy you bring to this project. Your feedback shapes every step, so please keep it coming. We’re here and happy to chat if any doubt arise.

WakeUp Labs Team

1 Like
12

Thank you @WakeUpLabs,

Excellent presentation. For future videos, please increase the resolution of the Excel screenshots. They aren’t clear in either the video or Figma.

The milestone has been approved. I will send you the instructions for the invoice soon.

CC @Geraldine

1 Like
13

Good morning @WakeUpLabs

We are two weeks behind on deliverables, and it’s the final week of the program. Do you have any news on the project’s status?

14

Hey @Yuelwolf, thank you for checking in and for your patience. As I shared with you privately, we are running behind.

The project required more understanding and discovery than we first anticipated so the outcome would be genuinely useful, and this coincided with the winter holidays. We also only realized last week that the program has hard deadlines. We had assumed those deadlines were mainly for new applicant intake. That assumption was our mistake.

The team is fully focused and advancing. We will close the core deliverables as quickly as possible so you can wrap up your tasks, and we will continue with the final polish without impacting the program’s commitments. Thanks again for the support. We will keep updates flowing here.

Thanks!

15

Hi everyone, hope you’re all doing well!
Just to share an update: we’ve already aligned with both the Domain Allocator and the DAO CORE team, and they were understanding of the delay.

From our side, we’ll do our best to make the milestone checks as smooth and easy as possible, so payments can be released right away once each milestone is completed. Thanks a lot for the support!