GrowBlocks
Home
Solutions
Cases
Knowledge
Design
Media
Public Chain · Consortium

Controls and clear access points

Multi-party evidence preservation alliance chain

PeriodAbout 1 month
Business LineConsortium chain / permission chain
Core StackCustomized consensus / permission models / node tools
RegionChina

Project Background and Challenges

The client is a traditional industry overseas team that requires a chain with controllable permissions and clear participants, for multi-party data verification and reconciliation. Compared to public blockchains, it places greater emphasis on block production certainty and access control.

A balance between decentralization and regulation— It is necessary to leverage blockchain's immutability to build multi-party trust, while also meeting participants' needs for permission management, auditability, and arbitrability.

The scope we undertake

Chain core (customized consensus, permission model), node access management, on-chain data proofing, cross-party reconciliation, supporting node tools.

Scope 1
Chain Core (Custom Consensus, Permission Model)
Scope 2
Node access management
Scope 3
On-chain data is preserved as evidence
Scope 4
Cross-party reconciliation
Scope 5
Supporting node tools

Technology stack

共识
Consensus
BFT-type custom consensus, block production certainty
权限
Authority
Node access and data access permission model
存证
Evidence is preserved
On-chain data is stored as evidence and reconciled with multiple parties
工具
Tools
Supporting node management tools

Key technical decisions

Decision 01
Consensus: PoW vs BFT
Choosing BFT-type consensus allows participants to achieve block certainty in clear scenarios and performs far better than PoW.
Decision 02
Permission model
Read and write permissions are set according to participant roles; sensitive data can be encrypted on-chain, and node permissions can be dynamically adjusted.
Decision 03
Supporting delivery
Node tools, monitoring, and upgrade mechanisms are delivered simultaneously on-chain, reducing operational costs for participants.

Delivery Success (Desensitization)

10000+ TPS
Chain throughput capability
10 s
Block Formation Deterministic Time
100 +
Connect with the participants

Teams and cycles

The total cycle is about 1 month, involving 10 people, and progressing in four stages:

01
Consensus and permission design
02
Core chain development
03
Supporting tool development
04
Participants connect and go online

Related Content

contact us

Want to see the complete Figma file?

Schedule a 30-minute technical consultation where we walk you through the most relevant Figma / Lanhu files for your project via remote demo, including all pages, component libraries, and interactive prototypes.