This week in Tari

This week in Tari

Tari’s DAN Layer is progressing nicely with a lot of pull requests (PRs) related to checkpoints and committees getting merged this week.
One exciting PR merged this week was
#4260: Add range proof batch verification to validators
More than 80% of CPU time during block sync and verification is taken up by range proof verification. Using a clever trick of using the same cryptographic generators, multiple range proofs can be verified at the same time, dramatically cutting down the time taken in verification.
Bulletproof+ benchmarks
have shown that range-proof verification gains for an empty block with only two outputs would be around 37%. A slightly more populated block with four outputs gains would be 56%, and then for a densely populated block (256 outputs or more) the gains would approach 80%. Effective speedup of block verification in these three cases would be around 30% for two outputs, around 45% for four outputs and around 64% for 256 outputs or more.
Here’s a list of other PRs recently merged:
Features
add checkpoint_number to checkpoint with basic base layer validations (
add encryption service (
add range proof batch verification to validators (
add tari engine for flow and wasm functions (
basic checkpoint validation (
add or_optional trait extension for RpcStatus (
contract acceptance signatures are submitted and validated (
validates non-contract utxos have no sidechain features (
track checkpoint number for each checkpoint submitted (
generate and add checkpoint signatures (
uses tip height to calc abs acceptance period (
Bug Fixes
add saturating sub to prevent potential underflow (
minor fixups for hex/type parsing and long running commands (
include issuer public key in contract id hash (
include state root in checkpoint signature (
scan and save contracts without autoaccept (
handle not found rpc error in utxo scanning (

Leave a Reply

Your email address will not be published. Required fields are marked *