You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, our offchain batch signature of entries uses the Pedersen hash. Which is O(n) and thus is a big bottleneck when a publisher wants to publish a lot of entries in one batch.
With the recent starknet.py bump, we can now use the Poseidon hash, which gives us ~60% better performances.
We want to update the revision field here to 1 so the Poseidon hash is correctly used by starknet.py.
This requires synchronisation with the pragma-node, we will need to update the way we check for signature correctness, see: astraly-labs/pragma-node#87
After that, test properly a publishing process from the price pusher to the API to be sure everything is ok.
The text was updated successfully, but these errors were encountered:
Feature Request
Current behavior
At the moment, our offchain batch signature of entries uses the
Pedersen
hash. Which is O(n) and thus is a big bottleneck when a publisher wants to publish a lot of entries in one batch.With the recent
starknet.py
bump, we can now use thePoseidon
hash, which gives us ~60% better performances.We recently made some investigations here:
astraly-labs/pragma-node#83 (comment)
Expected behavior
We want to update the
revision
field here to1
so thePoseidon
hash is correctly used bystarknet.py
.This requires synchronisation with the
pragma-node
, we will need to update the way we check for signature correctness, see:astraly-labs/pragma-node#87
After that, test properly a publishing process from the price pusher to the API to be sure everything is ok.
The text was updated successfully, but these errors were encountered: