Sandbox API Asks

💡 SIP: Ideas In Admin Review
61

Great to hear this response, it’s a solid first step.

On our end, once SIP-19 is finalized, we’ll be able to give more clarity on what would have been helpful from our side.

Anyway, feeling good about it and looking forward to seeing how it evolves!

4 Likes
62

Hello everybody!

We have the CTO’s attention on this. (He just chased me today). It’d be good to drive this home!

I would suggest to draft the ask so we can get the convo with TSB started

Who is up for a SIP? :flexed_biceps:

4 Likes
63

Already on it! :slight_smile: I’m just about done writing the initial draft with everything we’ve gone over in this thread.

3 Likes
64

What do yall think? @cryptodiplo @Gonzacolo @shont

SIP Title

  • Development of the Sandbox API for Player and Experience Data
  • Project Description
    • This SIP proposes the development of an official Sandbox API that enables external tools, developers, and community members (SandFam) to access a player and experience data. This API aims to access key information such as
      • wallet addresses,
      • KYC status,
      • ongoing and persistent saved variables,
      • quest completion,
      • total playtime,
      • and highscores.
    • By providing this data, Sandbox DAO can empower the community to build tools for tracking performance, distributing rewards, and enhancing gameplay beyond the native Game Maker ecosystem.

Proposal Details

Q6 What is the problem you are trying to solve?

  • Currently, Sandbox creators and community developers lack a method for accessing player-related data and game performance metrics. This limits the ability to build external systems such as leaderboards, custom dashboards, DAO contributor reward platforms, and gameplay-based token distribution mechanisms.
  • Without access to this type of information, many promising community-led initiatives are either incompatible or must rely on workarounds or methods that tend to lack scalability and reliability.
  • Many creators rely on undocumented or unreliable endpoints, or have no access at all to critical player and gameplay data. This bottlenecks creativity.

Q7 How can your solution solve this problem?

  • The proposed Sandbox API would provide authenticated and structured access to essential player and experience data, enabling the development of rich external systems that integrate seamlessly with in-game performance. Community developers could build tools for rewarding players with NFTs or tokens, tracking quest progress across experiences, hosting competitions, and displaying multi-metric highscores. This structure would unlock new layers of engagement, accountability, and creativity within the Sandbox DAO ecosystem.

  • We propose the development of an official Sandbox API focused on player and experience data. This API will provide endpoints for retrieving:

  • Player wallet addresses and KYC status

  • Quest progress and completion status

  • Saved variables and game states

  • Time played in specific experiences

  • Highscores, points, and other performance metrics

  • UGC data (e.g., avatars used)

Q8 What are the benefits to the Sandbox Ecosystem

  • Empowers creators to design richer, more interactive games
  • Enables data persistence and progression across experiences
  • Encourages cross-game interoperability and UGC economy growth
  • Improves retention by offering replayable and trackable content
  • Supports Sandbox’s ambitions of being a modular, data-capable metaverse

Q9 Provide a risk analysis of your project

  • Security Risk: Misuse or unauthorized access to player data. Mitigation: Use token-based auth, rate limiting, and data access permissions.
  • Implementation Risk: Technical debt or misalignment with existing architecture. Mitigation: Collaborate closely with internal engineering team and community contributors.
  • Adoption Risk: Low usage if documentation or ease of use is lacking. Mitigation: Deliver robust, clear API documentation and community examples.

Q10 Alternatives Considered

  • Relying on undocumented endpoints (not sustainable or secure)
  • Using third-party workarounds (e.g., screenshot-based analytics, custom UGC triggers)
  • Delaying until a full SDK or in-engine data pipeline is released
3 Likes
65

Thank you for the visibility on SIP proposal structuring.
It’s really useful as we prepare to start a discussion on SIP for advanced online builder technology to turbocharge community creative tools and Sandbox community expansion and engagement!C :rocket:

3 Likes
66

What are your thoughts? Do you think I captured everything in the API ask?

2 Likes
67

Maybe could be good to know user inventories in wallet.
This is something we could greatly leverage for the online web builder.
Knowing what NFTS/Assets a user holds in wallet when connected could enable to provide utility for those assets.

1 Like
68

We have other APIs like alchemy that can show user NFTs by wallet, think it is probably best to limit the Sandbox API to only Sandbox specific things we can’t get otherwise.

3 Likes
69

I also think this is something everyone in the community has been wanting for a while. The more API endpoints we get—like for saved variables, playtime, quest progress—the more creative and dynamic experiences we can build.

Of course, building a robust and secure API will take time, and that’s totally understandable. But even if it rolls out step by step, it’ll be a huge win for creators and the ecosystem as a whole.

4 Likes
70

This has great potential :clap:t4:

Documenting the community needs so TSB can develop API endpoints is a HUGE step forward.

Thanks for taking the time to summarize things here, @Lanzer :rocket:

2 Likes
71

I also want to add that this is so important to me, I would vote for funding 2 years of backend developer salary for TSB to use to focus exclusively on this, if they have bandwidth concerns on their side.

@theKuntaMC @Lanzer @Cyril Do you think this would increase the likelihood of success here?

3 Likes
72

If the proposed funding made enough sense to the community to garner the majority of VP, it would pass the vote.

But it’s hard to say… :crystal_ball:

1 Like
73

It’s great to see this moving forward — having the CTO engaged is a game changer!

Thanks, @Lanzer, for drafting the initial SIP.

WakeUp Labs fully supports this initiative and will contribute as technical experts.

Given the complexity of the task and the previously discussed bottlenecks, we believe it needs to be approached with a product and engineering mindset, not taken lightly.

We propose allocating budget for a team of capable DAO members to drive this initiative forward, with WakeUp Labs leading the engineering side, supported by people overseeing development, executing growth, and launching marketing initiatives. And, as @cryptodiplo suggested, allocating budget for TSB resources.

Working closely with TSB is essential to accelerate processes.

To move forward, we propose:

  • Using Lanzer’s SIP template in a shared Google Doc to collaboratively draft the value proposition, key questions, and a formal project scope — defining deliverables, technical requirements, and clear project boundaries. [Link Here]

  • Opening a direct communication channel with a TSB Tech Lead.

  • Organizing feedback sessions with TSB to refine the document with the Sandbox API Working Group.

We believe these next steps are crucial for exchanging ideas with both TSB and the community — and ultimately for preparing a formal proposal that’s truly aligned with everyone’s needs and priorities.

1 Like
74

Thanks for the good work @Lanzer !

Actually to get the ball rolling we dont need to go that far and start documenting the full SIP. Just focusing on well specified data points is enough! That will enable me to have a good convo with the tech folks.

It’s not a question of funding but only a question of priorities. The product teams plates are full, and their priorities are changing regularly to adapt to the market and to the current opportunities. The unfortunate reallity is that even if they would agree to do a piece of work requested by the DAO (by ways of SIP) there is no guaranty that they will deliver as promised.

However what is promising is that we have the CTO attention. It’s very encouraging!

4 Likes
75

I mean dang, I was going to go for 1 year but 2 years sounds fine with me if you think that’s a more solid route. Maybe we do a review at 1 year to see if we want to continue with the team we’ve chosen? I can’t imagine it will be a difficult thing to develop and maintain. APIs are a pretty known thing.

I have some price estimates but I definitely didn’t account for 2 years :laughing:

I estimated about 100K SAND ($30K) to get it out the door and usable by the community, but I need to speak to a few more developers to see how realistic that number is and then 2x for 2 years.

Thoughts?

1 Like
76

I have the entire SIP already fully drafted in a Google Doc, I only copy pasted some of the questions that seemed most applicable to what was being asked in this thread. There are other questions like milestones, budget, points of contact, etc that is required in a full SIP.

with WakeUp Labs leading the engineering side

I hadn’t realized you wanted to be a developer for this. My work week is really intense right now, but perhaps we could make an X space out of this @theKuntaMC ? Might be a pretty cool thing to X space out a call between a SIP author and a dev.

2 Likes
77

Okay, sounds good! I have the SIP fully done from a project manager standpoint with a lot of technical input from this thread and others. I haven’t partnered with a developer yet. But as you can see Wakeup Labs has already offered

Is there something I need to do regarding the CTO, or should I give you some time to advise how I should proceed with that?

2 Likes
78

As I understand this…
With APIs, we face the same obstacle as we do with the Smart Contracts for the estate-level LAND sales, in that these are features that TSB will want to design internally, rather than contracting third parties.

So, just a heads up to @WakeUpLabs and others…

At this point, Cyril has the attention of the CTO on this matter, and the best thing we can do is pass along the list of data points that @Lanzer has already compiled above.

@Cyril – does Lanzer’s summary (above) suffice for advancing the conversation at this point?

2 Likes
79

Hello all,

Just for the sake of clarity, the build will be made by TSB, so we don’t need to scope out cost etc.

The very first step is to document the data points, to get a temperature check with TSB. I assume it is the below list @Lanzer?

Once they confirm feasibility, a strong support for this SIP will really send a positive message

3 Likes
80

Edited the response due to me misunderstanding Cyril post above

edited out text here

I must have missed a conversation somewhere.

There was API conversation throughout the forums, then @cryptodiplo started this thread exploring a community SIP for API.
Sandbox API Asks

Community discussion ensues. We build out what we’re after.

Kunta asks who wants to take the SIP.
Sandbox API Asks - #43 by theKuntaMC

I volunteer and put my team to building the entire SIP. Takes time, effort, and money I could’ve spent elsewhere.

I post SIP for community feedback before submitting…Now SIP has transitioned from my hands to a DAO Admin team project.

Between this and a few other SIP review things going on right now I’m feeling really frustrated, cue this post here
Governance Food for Thought 🏭 we're a SIP factory - #4 by Lanzer

3 Likes