Tetcore ·

🚀 Tetcore enables the rapid prototyping of blockchains built for any purpose.

Trying it out

Simply go to core.tetcoin.org and follow the installation instructions. You can also try out one of the tutorials.

Contributions & Code of Conduct

Please follow the contributions guidelines as outlined in docs/CONTRIBUTING.adoc. In all communications and contributions, this project follows the Contributor Covenant Code of Conduct.

Security

The security policy and procedures can be found in docs/SECURITY.md.

License

• Tetcore Primitives (tp-*), Fabric (fabric-*) and the nobles (nobles-*), binaries (/bin) and all other utilities are licensed under Apache 2.0.
• Tetcore Client (/client/* / tc-*) is licensed under GPL v3.0 with a classpath linking exception.

The reason for the split-licensing is to ensure that for the vast majority of teams using Tetcore to create feature-chains, then all changes can be made entirely in Apache2-licensed code, allowing teams full freedom over what and how they release and giving licensing clarity to commercial teams.

In the interests of the community, we require any deeper improvements made to Tetcore's core logic (e.g. Tetcore's internal consensus, crypto or database code) to be contributed back so everyone can benefit.

lib.rs:

Node authorization noble

This noble manages a configurable set of nodes for a permissioned network. Each node is dentified by a PeerId (i.e. Vec). It provides two ways to authorize a node,

• a set of well known nodes across different organizations in which the connections are allowed.
• users can claim the ownership for each node, then manage the connections of the node.

A node must have an owner. The owner can additionally change the connections for the node. Only one user is allowed to claim a specific node. To eliminate false claim, the maintainer of the node should claim it before even starting the node. This noble uses offchain worker to set reserved nodes, if the node is not an authority, make sure to enable offchain worker with the right CLI flag. The node can be lagged with the latest block, in this case you need to disable offchain worker and manually set reserved nodes when starting it.