Hello Folks,we’re proud to announce something different. This is not a coin or proof of process announcement thread – this is a technology announcement thread. So sadly for you there is no ICO, nothing to buy or sell, but we really hope to open up a good discussion about features, problems and maybe we can find the one or other person who might be interested in joining our DEV team.
First a few words to our team:We‘re TrustChainTechnologies, with members mainly from the the DACH region (Austria, Germany, Switzerland) and based in Austria. Our core team consists of about 20 persons, ranging from DEVs, designers, marketers, crypto enthusiasts and some who might categorize them differently. Our lead developer is FireMail, born 1986, who graduated summa cum laude in 2009, specializing in database architecture and cryptology. Our crypto enthusiasts run the biggest German speaking Facebook group for cryptographic currencies (
https://www.facebook.com/groups/1058102100972677/) with about 16.000 members – if you’re from that group „Hi there.“
So what is our motivation:In our point of view the number of altcoins running their own chains is growing so rapidly that they most likely will run into one problem sooner or later – lack of physical hardware to support the network security. Some projects try to avoid this problem by having a PoW phase before switching to some kind of PoS or hybrid algorithm, but this fix is mostly just for a short period of time. As soon as the miners found all the PoW blocks and the algorithm switches to PoS for example, the miners remove their calculation power and use a single wallet for staking. This leaves smaller altcoins with the problem that they become vulnerable for attacks.
Something else we discovered was the lack of real innovation for most coins. 90% or even more of the source codes are just forked from BTC github and the changes are mostly made in the proof of process part (e.g. PoS instead of PoW). This leaves every single altcoin with a bunch of code that the DEVs mostly haven’t even read or they ignore it since it’s not relevant for a fast ICO / fast release of the coin. But what happens when there is a bug because it’s an old fork and hasn’t been updated? What happens when there is an improved way for communication processing, block storing or other core features? Wouldn’t it be much better when DEVs could focus their manpower on real innovations rather than on reworking foreign code?
So what is this MetaChain now?
The MetaChain is a technological construct that provides the basic code set for multiple blockchains to run separately in one environment. You can imagine the MetaChain as OSI-Layer which encapsules different features (see below), allowing a DEV to save time in development without loosing the flexibility of working directly in C++.
Features of the MetaChain (Please note that all these features are platform independent and their functionality can be configured, enabled and disabled by the user):
- MetaChain (https://forum.trustchaintechnologies.io/Thread-MCP02-MetaChain-and-SubChains)
- Changes in the MetaChain are proven through a new algorithm (which is coin based and a subchain in the MetaChain, ANN Thread for this coin will follow) so that all changes are chained and transparent
- n SubChains can run parallel
- Adding subchains during runtime
- Automated 1-Click creation of SubChain within the whole Network (assuming that the creator uses standard and default provided proof of process)
- New / custom proof of processes or workflows for coins can be loaded dynamically through factory design pattern (https://forum.trustchaintechnologies.io/Thread-MCP04-individual-Subchain-handling)
- White- & Blacklist for proof of processes and workflows
- White- & Blacklist for SubChains (so you can support only the SubChains you like or invested in)
- Full and Light nodes (Full nodes store all activated SubChains’ blocks, light nodes only relevant information)
- Blocks and Transactions can be completely customized within a coin workflow allowing for non-coin based blockchains (https://forum.trustchaintechnologies.io/Thread-MCP03-Blocks-and-Transactions)
- Default provided Proof of Process Modules: PoW, PoS
- Default provided Workflow Module: Coin based currency
- Network communication:
- P2P peer sharing
- Local ban list upon defined number of bad requests
- Auto update of the basic framework from trusted and secure locations
- SSL secured communication
- Own communication protocol for SubChains to use the network connections to the fullest extend (TCP as network protocol)
- Storage Management:
- MetaChain uses rocksDB (http://rocksdb.org/) for meta information
- SubChains have their separate environments
- Flexible storing of SubChain meta information:
- User configurable backend DB engine
- C++ Interface for DEVs to write code for new backend Engines
- Loadable engine modules to add those new backend Engines
- Default provided engines: rocksDB and MySQL
- Storing of raw blocks:
- Configurable max_size of the raw file, allowing to move old files to slower storage units
- Binary storing to achieve full flexibility for the DEVs of SubChains
- Storing of meta information of blocks for faster raw block processing
- Cryptology:
- All encryptions are SHA3
- Including KECCAK, KMAC, SHAKE
- Quantum attack safe!
- ~1000% better performance than BTC hmac hashing (please note that this number was calculated in a non-scientific way with limited time measuring capabilities but comes from the 2048 iterations in hmac hashing, where SHA3 KMAC uses a sponge-squeeze principle, removing the need for iterations. SHA3 512 KMAC was done successfully on release-build, regular win10 machine (i7) with no optimization and system-based timers within 22 microseconds. It could be that the SHA3 KMAC is even faster when using high performance external timers, non-windows system and optimized building.)
- Wallet-Address (https://forum.trustchaintechnologies.io/Thread-MCP01-Account)
- One private key for all SubChains
- Each SubChain wallet address changes 90+% of the bits for the same private key
- Including BIP39 (renamed to MCP39 due to massive changes) (https://forum.trustchaintechnologies.io/Thread-MCP39-Mnemonic)
- secp256k1 parallel to secp256r1 ECDSA, allowing smart devices to use inbuilt encryption chips rather than software signing, thus removing the chance of memory collision signing attacks
Use CasesTo show you why we chose to develop the MetaChain, we want to provide you with three use cases:
1) Automatic PoS StakingA node can be connected with a wallet to enable staking. Every private key within the MetaChain works on all SubChains, but every SubChain wallet address is different for the same private key. This means that we don’t have a security impact, but a general wallet for all SubChains. So when there are for example 10 PoS Coins within the MetaChain network and you hodl all of them, you only need one active wallet but participate in 10 PoS at the same time. This saves energy, hassle for possible updating of clients, easier backups and improves usability.
2) DEV time savingWhen you’re a DEV in blockchain technology you know that time is always a limited factor. So working on your own bitcoin fork to enable a different algorithm, that maybe has random airdrops and allows to push random binary data into the blockchain. There is so much you need to work around that has no real innovation: storing mechanisms, network communications, removing old code that’s not needed anymore, fixing bugs because other code suddenly relied on this old code etc.
With the MetaChain you simply use a coin based workflow as provided from github, maybe overload the block structure, use API calls for network communication and upload this module for all to use. This is a huge timesaver which doesn’t remove your flexibility in development – so that DEVs can focus on innovation, rather than preparation.
3) Enlarging NetworkMost altcoins lack of supporting devices / hardware since they’re not well known or maybe they’re too complicated to be installed or something else didn’t work. When using this module based structure all participating MetaChain Nodes can enable your SubChain (or maybe they used a *-whitelist so all SubChains are allowed) which widens an altcoins number of nodes without the need of installing new software. In software design there is a principle that the barriers for a user need to be as little as possible to enhance his user experience - just imagine a user that can enable SubChains on his PC with a simple click.
Network enlargement works for all SubChains and everyone helps everyone – why? Every new project on the MetaChain will target new users which might enable more than just one SubChain, thus enlarging the network without the need of additional software or steps.
Conclusion and FutureWith the MetaChain we aim at providing a basic code set so that developers can focus their time on innovation rather than reworking old code. Another huge plus is that they can rely on a bigger hardware network with a settled community – when working with default provided modules the coin will run out of the box, without any additional steps.
By using the newest NIST approved hashing standard SHA3 all SubChains are also quantum attack safe and have great performance by using the sponge-squeeze principle.
With the usage of rocksDB as meta information storage backend we also used a very new, but heavily dynamic and optimized storage engine which allows very fast IO.
Currently there are two Coins which are actively developed for the MetaChain. These coins will be later announced in their own threads and linked here. If you want to get informed what those two coins are, please subscribe to this thread.
If you are a developer, a group of developer, some guy with mad graphic skills or think you can somehow help our team, please don’t hesitate to ask.
We’re more than just happy to welcome you onboard!Links- Website:
https://www.tct.io- Facebook:
https://www.facebook.com/TrustChainTechnologies/- Twitter:
https://twitter.com/TrustChainTech- Forum:
https://forum.trustchaintechnologies.io/- Slack:
https://join.slack.com/t/trustchaintech/shared_invite/MjM4NDgzNjU2MTI5LTE1MDUxMTE4MzktOTI3YTEyMWZhZQ- Github:
https://github.com/TrustChainTechnologies- Telegram:
https://t.me/TCTmetachain
Show Posts
