One week technical update express of substrate and Boca 20220425 - 20220501

This is a week of crazy output ,  A lot of updates and releases :

Nomination Pools  complete ,  And online westend test

In last week's staking slash After the algorithm is updated as a preliminary , Nomination Pool Module passing 2 Months of development ,  Finally, it is basically completed this week .

Nomination Pool

It's a new nomination mechanism ,  Current " pledge / Nomination " The main ways are

1 For more than

The way ,  That is, a single nominee can choose up to 16 Verifier candidates ;  and

Nomination Pool

Then the user can initiate a " Nomination pool ",  Other users can choose to join the nomination pool ,  This nomination pool can only nominate one verifier candidate at a time ;  This is equivalent to more

"  For one more "

The way of nomination .

But the same user can join multiple Nomination Pool,  It is also equivalent to indirectly realizing " Many to many " In the form of . Nomination Pool Its main function is to expand the diversity of elections ,  To improve network security .

Nomination Pool

The implementation mechanism of is complex ,  So it should be in the test network first westend Go online first ,  Then deploy to Kusama,  The last is Polkadot.  The emergence of this way ,  Undoubtedly, it has increased the diversity of the economic ecology of Poka .

Uniques Pallet  increase NFT Lock function

Uniques Pallet It's Boca ecology NFT The basic module of ,  And Boca's NFT standard RMRK It is required to be NFT Get into

market

On sale ,  There must be one

locking

Locking mechanism :  In other words, enter

rmrk-market

Of NFT Must be locked and cannot be modified arbitrarily .

because RMRK The module is currently from

uniques

Module extension ,  So users can use Uniques in Call Come around RMRK Lock in ;  therefore

Unique Pallet

  Added a

Locker

Of trait,  There's a

should_check_lock

Method returns a bool Value to indicate whether it is locked ,  Also for

()

It's time to trait And returns... For this type

false

,  In this way, there is no lock by default .

wildcard RPC Subscription is set to

unsafe

In the future ,  Use wildcards to subscribe to all stored updates on the chain RPC API Will be set to  

unsafe

,  That is, when updates are stored on the subscription chain key Parameter set to  

None

when ,  The client's subscription will be rejected ,  At the same time, it will be informed by the service node that it is not secure RPC The way ,  Unless the node is running with  

--rpc-methods=unsafe 

Options .

The reason for this update is that some developers find that wildcards are used to subscribe to updates on the chain under certain conditions ,  There is a certain probability that the node data has been updated but the new data has not been correctly returned to the client ;  After analysis, it was found that

best block

and

final block

  Data differences and data lag caused by asynchronous subscriptions .

After a discussion ,  Finding it difficult to fully implement the full data consistency of the desired subscription , CAP principle rules!  Finally, to be on the safe side ,  It was decided that RPC Set to unsafe.

Client added chain-info  Sons command

Add a new one

chain-info

  Sons command ,  Used to print the current

Stored in a database

Metadata ,  Include :

• best_hash
    Current best chunk hash

• best_number
    Current optimal block height

• genesis_hash
    Genesis hash

• finalized_hash
  Current final acknowledgement block hash

• finalized_number
  Current final confirmation block height

Use mode:

./binary chain-info --base-path=PATH_TO_DB --chain=CHAIN --pruning=PRUNING

The results are similar to the following :

{"best_hash":"0xbfc95e0d9864d8fe7a2cc2fd2af298d68fb5f9fe6bad8529545ec981ba677efa","best_number":10,"genesis_hash":"0x3a1beb9351d4d004e0c19f92dac659c2a356e1c0dcd4f38a93ee02dc1acd98f5","finalized_hash":"0x3a1beb9351d4d004e0c19f92dac659c2a356e1c0dcd4f38a93ee02dc1acd98f5","finalized_number":0,"finalized_state":["0x3a1beb9351d4d004e0c19f92dac659c2a356e1c0dcd4f38a93ee02dc1acd98f5",0]}

This subcommand can be used offline ,  That is, no node operation is required .

This paper is about SEP Creation  Original group articles ,  By pengyalun

Permanent link address

Unauthorized ,  Do not reprint .