RubySDK · Decentralised marketplace infrastructure
Decentralised marketplaces, for whatever your asset is.
Coins, watches, art, a share of a building. We are building a component toolkit for the front end your users see. Underneath it we take care of the private exchange, on the decentralised privacy infrastructure that suits the asset.
RubySDK is a professional Web3 consulting practice that works with complex data.
What you could build
A marketplace for an asset that does not have one.
Most tokenisation is of financial assets: funds, credit, treasuries, equity. Our interest is in what that leaves out.
The assets.
Things that exist outside the financial system and are owned outright. Property. Art. Collectibles like watches, wine and coins. Ordinarily they are bought and sold whole.
- Property
- Art
- Watches
- Wine
- Coins
Fractional ownership.
A token can divide the asset into parts. An owner can sell a quarter of a building or a tenth of a painting and keep the rest. A buyer can take a share of something they could not have bought whole.
Held directly.
Each part can sit in the owner's own wallet. No custodian holds it for them, and no platform stands between them and the record of who owns what. A transfer settles between the two parties.
Beyond the assets.
The same stack runs further than ownership. We have built entire ecommerce systems on it, for food and drink and apparel.
- Food and drink
- Apparel
How the work splits
You own the front. We take care of the exchange.
Your users see your marketplace. What happens underneath it is ours.
What you build.
The interface your users see, in your own name. The listings, the pages, and the way buying and selling works. You decide how it looks and how it behaves. We give you the components to build it from.
What we take care of.
The exchange underneath. The token, the record of who is allowed to hold it, the transfer that settles, and which decentralised privacy infrastructure it all runs on. Tokenisation is how that is done.
What you get
The components you build the marketplace from.
These are the parts of the exchange. All of them can be managed programmatically or via user interface, so your own front end drives them.
Token factory
Creates the token for your asset and sets its supply, units, rules, read and write approvals, issuance and balances.
Holder registry
Holds the list of who is approved to hold the token, and the controls to add and remove users.
Confidential transfers
Checks the registry first, so a transfer to someone not on the list does not settle, and keeps the details unreadable to outsiders.
Redemption
Lets a holder give the token back and take the asset, or the value of the asset, in return.
The token standard, the chain and the contract language are settled in the architecture phase against your requirement.
Underneath
Where the private exchange runs.
We architect solutions on existing privacy infrastructure, ensuring balances and transfer information is protected from everyone without explicit permission. Which of these suits your asset is settled with you.
Privacy chains.
Assets sit on a network that hides balances and transfers as a property of its cryptography.
- Oasis Sapphire
- Secret Network
Privacy wrappers.
Assets sit on a transparent network and a cryptographic privacy layer wraps it.
- Silent Data, from Applied Blockchain
Private networks.
Permissioned platforms separate data so only the parties to a transaction hold it on their nodes. Canton is a network you join, and you build your own on Corda or Hyperledger.
- Canton Network
- Corda
- Hyperledger
Token standards.
ERC-3643 is the permissioned token standard for real-world assets on Ethereum-compatible chains. It is selected in the architecture phase, as everything else is.
- ERC-3643
RubySDK works across other networks, identified during the ecosystem assessment.
Who it is for
Who runs the marketplace.
Three kinds of client, and the same division of labour in each.
A company with an asset of its own
For businesses that own a real-world asset and want it transferable to a controlled group without publishing its holder list or transaction history.
A platform whose clients bring the assets
For businesses providing a service where clients issue assets.
A marketplace that already runs
For platforms with existing products and a user base that need a private exchange underneath.
The principals’ experience across
Financial services · Healthcare · Insurance · Professional services · Logistics · Real estate · Industrials
How we work
Our Services.
You can engage RubySDK for a single phase or for all of the following services:
Definition
- Business analysis. What the asset is, who the parties are, and how it is managed today.
- Use case. What has to be transferable, to whom, what has to stay private, and what has to be reported.
Architecture
- Ecosystem assessment. The third-party platforms and components a solution could be built from, tested against your requirement.
- Solution design. What gets built, what gets bought, how the components integrate.
Prototype
- Working prototype. An outline Product Requirements Document (PRD) is used to build a proof-of-concept or prototype in a sandbox.
- Iteration. The solution is iterated on feedback from testing with real users, informing UI and UX decisions.
Development
- Specification. The final PRD is specified in detail according to the results of the prototype evaluation.
- Project management. We contract the build out and manage the development of the minimum viable product (MVP).
Production
- Independent audit. We arrange the review of the contracts and the privacy properties by an accredited party.
- Deployment. The MVP is deployed and we remain engaged for ongoing support and future feature developments.
Who you work with
The principals.
Joel Smalley and Mark Abbott have worked together for ten years.
Joel Smalley
Co-Founder of RubySDK.
- The technical and product work.
- Architecture and solution design.
Mark Abbott
Principal of RubySDK.
- The commercial work.
- Project and relationship management.
Contact