labs@atheron:~/services/blockchains$ chain init --private --spec
Blockchains
Private and public, specified before they are built.
Permissioned networks for companies that need a shared record they can trust. Public networks with explorers and wallets. Either way, we write the specification first, then the node.
// what we build
The network and its tools.
01
Private networks
02
Public networks
03
Explorers
04
Wallets
05
Bridges and integrations
06
Specifications
// how we build it
The specification is the product.
- Every rule is written down and dated when it is settled. The code implements what is written.
- Anything not decided is marked undecided, never filled in with a guess.
- A private chain is often not the answer. We will tell you when a shared database would do.
- Public launches are fair. What is issued, to whom and when is disclosed before the first block.
// stack
What we usually build with.
- nodes
- Rust or Go, chosen with you
- consensus
- Proof of work, proof of stake, or a permissioned protocol, as the network needs
- explorers
- Next.js and PostgreSQL
- infrastructure
- Nodes on DigitalOcean, AWS or your own Lenovo ThinkSystem servers
// a typical first project
A private network proof of concept.
A small permissioned network, a simple explorer and one integration with your systems, so you can prove the idea before you commit. Open it in the estimator to see what it would cost.
// proof
The ATON blockchain
A block-DAG ordered by a GHOSTDAG-style rule, with a hard cap of one billion ATON and a fair launch, specified in public.
// questions
Questions about blockchains.
Do we need a blockchain?
Often not. If one company controls the data, a database is simpler. A chain earns its place when several parties need one record that none of them controls alone.
Private or public?
Private when the members are known and the data is not for everyone. Public when anyone should be able to join, read and check it.
Who runs the nodes?
For a private network, each member usually runs one, and we can run them for members who would rather not. For a public network, anyone can.
How long does a network take?
A proof of concept takes weeks. A public network takes many months, most of it in the specification and the testing.
// industries
How it fits your industry.
See what this looks like in your industry: the questions buyers ask, and example projects with a price range.
// related
Often built together.
// where we work
Find your market.
See this work from your city: what changes there, the questions buyers ask, and prices in your currency.
// start
Not sure which you need?
Tell us the problem, not the solution. We will tell you what we would build, and what we would not.