3 - Opening Access to StrongholdNET
This proposal asks which set of APIs should be prioritized for development and release in the StrongholdNET open-access developer console.
Outcome: Choice 3 - US bank to distributed ledger SHX settled USD payment APIs
Snapshot Time
Sep 8, 2024 20:00 GMT
Ledger Sequences
Stellar: 53,407,636 Ethereum: 20,715,302
Vote Start
Sep 9, 2024 20:00 GMT
First included Stellar ledger: 53,422,610
Vote End
Sep 13, 2024 20:00 GMT
Last included Stellar ledger: 53,482,389
Results Published
Sep 24, 2024 20:00 GMT
Implementation
Q1 2025
Description
Stronghold is opening access to certain StrongholdNET services to the wider developer ecosystem. This proposal asks which set of APIs should be prioritized for development and release in the StrongholdNET open-access developer console.
Developers not affiliated with existing StrongholdNET members, in most jurisdictions, will be able to sign up and interact with certain released StrongholdNET services and endpoints in a sandbox environment.
Background
StrongholdNET APIs are currently available only to developers affiliated with StrongholdNET members: developers working for customers or partner technology providers. Stronghold wishes to open access to certain APIs, allowing the wider ecosystem to understand better the functionality and principles behind some of StrongholdNET's capabilities.
To provide access to and assist development, Stronghold will release a developer console that is open to the public. The console will allow for the issuance of API keys that can be used to call the endpoints in a sandbox environment, allowing for development and testing of code that integrates with StrongholdNET.
Existing functionality will need to be adapted to work better in sandbox environments and outside of the context of the rest of the StrongholdNET APIs, so effort is required to 'port' over features. Some additional work is required to ensure full coverage of relevant ISO20022 message types, since some older areas in StrongholdNET support messages only to satisfy particular partner companies (and their specific workflows).
Distributed ledger to US bank stablecoin payment APIs Allows for the settlement of certain USD-denominated stablecoins from distributed ledger technologies to a US bank account.
Distributed ledger to US bank USD settled SHX payment APIs Allows for the transfer of SHx from distributed ledger technologies to a US bank settled as USD (i.e. an currency conversion occurs).
US bank to distributed ledger SHX settled USD payment APIs Allows for the transfer of USD from a US bank account to distributed ledger technologies settled as SHx (i.e. an currency conversion occurs).
These API endpoints will be made available in both RESTful JSON format as well as allow for the submission of ISO20022 XML messages to effect transmission. Stronghold notes that most developers will not have access to tooling that allows for interacting with ISO20022 messages and sees these endpoints as potentially beneficial to developers looking for experience with this standard.
Voting Notes
The vote asks which StrongholdNET APIs should be prioritized for development and release in the open-access developer console.
Distributed ledger to US bank stablecoin payment APIs
Distributed ledger to US bank USD settled SHX payment APIs
US bank to distributed ledger SHX settled USD payment APIs
The choice with the highest vote will be prioritized for first release in the developer console.
Results
A total of 173,263,197 voting power participated in the proposal vote.
Question
Which StrongholdNET APIs should be prioritized for development and release in the open-access developer console?
Choice 1
Distributed ledger to US bank stablecoin payment APIs
11,896,640
Choice 2
Distributed ledger to US bank USD settled SHX payment APIs
45,090,814
Choice 3
US bank to distributed ledger SHX settled USD payment APIs
116,275,743
Outcome: Choice 3 - US bank to distributed ledger SHX settled USD payment APIs
Last updated