Tech overview
TM2 Distributed ledger technology
The TM2 distributed ledger is a private and permissioned database that is shared, replicated, and synchronized among the trusted members of the TM2, ensuring that the ledger is updated only with network-verified transactions by approved parties. The distributed ledger records the transactions on the TM2. Every record in the distributed ledger has a timestamp and unique cryptographic signature. The ledger is an auditable, immutable history of all transactions in the network and at all times visible to the verified members of the TM2.
TM2 Registry
The Registry Service holds the entire register of all investors that have been approved to transact on the TM2 and includes their trading status, permissions and Compliance & AML manifestations. All approved parties to the TM2 will have the ability to view all transactional history. Anyone will be able to register and join the TM2 after suitable verification of their identity. Each investor is identified by a unique ID, built from a hash of personal information that allows identification in a privacy-safe and secure way.
TM2 Compliance Technology
The Minfinium Compliance technology has transfer() and transferFrom() validation calls occurring during the movement of every digital metals coin. It will check the sender and receiver address within the Registry and enforce any applicable restraints using the registry as an authority on identity.
The metals coin restricts coin holders from trading to any address that has not passed the required verification process.
The restrictions provide issuers assurance that their metals coins will only be held by authorised investors in full compliance.
TM2 Transactions and validation
This is a Centrally Cleared, Private & permissioned distributed ledger. Validation is necessary either by the network operator(s) or by a network of trusted validators.
The power to transit information is distributed among a network of servers, instead of being driven from one primary source with as many trusted servers as possible so that the network will run successfully even if some servers fail.
Like a traditional ledger, the Minfinium digital metals ledger records the list of all transactions belonging to every single account on the network.
A complete copy of the global network is hosted on each server that runs Minifinium digital metals software. Any entity can run the TM2 digital metals software. These servers form a decentralised server network.
Trusted nodes reach consensus on the platform to have a new transaction persisted to the network. Every node in the network is aware of which other nodes are Trusted nodes.
This is not a decentralised operation or setup. Our distributed ledger operates as a closed, secure database and is centrally managed by the TM2.
Replication of the distributed ledger to members of the TM2 ensures that the shared ledgers are exact copies and lowers the risk of fraudulent transactions, because tampering would have to occur across many places at exactly the same time.
TM2 Security
The TM2 system has been built with several technological and practical considerations in mind.
Powerful Natural Safeguards
Only verified and registered users can use the TM2 market.
All digital metals including the BRD are 1:1 backed by physical metal. Digital metals such as the BRD take their intrinsic value from being 100% backed by metal. There is always physical backing and that means that as long as the physical metal is safe, the digital asset belonging to the rightful owner can always be restored.
Unauthorized actions can be stopped, blocked or rolled back, An identical copy of the ledger is synchronized and replicated constantly.
Since the TM2 is not a decentralized ledger system, the TM2 administrator has the ability to immediately stop, block or roll back any suspicious activity.
Risk name | Activities to minimize | Mitigation Approaches |
---|---|---|
TM2 platform Failure |
|
Users contact the vaults directly to retrieve their assets |
Stealing user website account password |
|
|
Stealing user private key |
|
|
Forgetting or losing the user account password | The user independently changes or recovers the password | |
Unfair investor uses the system | KYC/KYB procedures | Permanently block user |
Issuer trades unbacked product | Vault/Issuer position mirror-checks | Burn unbacked product |
Forgetting or losing the private key | Permanently block user public key and re-issue digital metals to the user | |
Platform infrastructure failure |
|
Restore system from backup
|
Errors in code |
Regular regression testing of the entire system after updates
|
System update to fix bugs |
Developers sabotage |
|
|
System administrators sabotage |
|
|
Losing systems administrators private key or account password |
|
Temporarily stopping the system, changing administrator keys and restoring the system starting from an uncompromised block |
Attempts to withdraw the money stolen from digital metals platform as a result of hacker attack |
|
Making a legal claim against the perpetrator |