Display currency parameters

The parameter view (here Cesium v1 for reference), will be useful in dev mode and for people to understand better Duniter-v2.

This will only interact with Duniter RPC api in its simplest form (key / value requests). Example is available in Ğcli: https://git.duniter.org/clients/rust/gcli-v2s/-/blob/4e1da26b3db40f61b14ef05bd716f4ba98e5f3f2/src/commands/runtime.rs

This currently gives this result:

> gcli -n local blockchain runtime-info
--- identity ---
confirm period: 40 blocks
validation period: 876600 blocks
autorevocation period: 5259600 blocks
deletion period: 52596000 blocks
change owner key period: 100800 blocks
identity creation period: 50 blocks
--- certification ---
certification period: 15 blocks
max certs by issuer: 10
min received cert to issue cert: 2
certification validity: 1000 blocks
--- wot ---
first issuable on: 20
min cert for membership: 2
min cert for create identity: 2
--- membership ---
membership validity: 1000 blocks
--- smith members ---
max certs by issuer: 8
min cert for membership: 2
smith inactivity max duration: 48
--- distance ---
max referee distance: 5
min accessible referees: Perbill(800000000)
distance evaluation price: 10 ĞD
--- currency ---
new account price: 3 ĞD
max new accounts per block: 1
existential deposit: 1 ĞD
--- provide randomness ---
max requests: 100
request price: 20 ĞD
--- universal dividend ---
max past reevals: 160
square money growth rate: Perbill(2381440)
UD creation period: 60000
UD reeval period: 1200000
units per ud: 10 ĞD

Some small explanation text can be added as well.

changed title from Display parameters to Display currency parameters

mentioned in issue #4 (closed)

assigned to @txels

mentioned in merge request !14 (merged)

I've started implementing this page in !14 (merged) using Cesium 1 as a reference, however I'm having difficulties mapping the values I get via the consts API listed here with the ones shown from v1.

I don't know enough about the differences between v1 and v2 blockchains to understand which parameters still make sense or not, or whether I should forget about what's included in the v1 page for now and focus on showing the parameters you've listed here that I can get via the polkadot JS API.

Another question is, what are the units for the "periods" listed here (e.g. UD reeval period: 1200000)?

Some guidance will be most welcome @HugoTrentesaux @blavenie

It seems to me that all the variables in this page are relevant in v2 too.

All the parameters are available in the pallet frame::Config implementation. For exemple for UD reeval period, it's here /pallets/universal-dividend/src/lib.rs#L81

/// Universal dividend reevaluation period (ms)
#[pallet::constant]
type UdReevalPeriod: Get<Self::Moment>;

So you can search for #[pallet::constant] and will find most of the consts.

I did not played with the constants js API yet, but in rust it looks like:

#            ↓ API             ↓ key
let value = api.constants().at(&runtime::constants().universal_dividend().ud_creation_period());

It's a simple key/value access. However since these are runtime constants, they can evolve with the runtime. See this slightly outdated post for more info about which constants can evolve and which can not: https://forum.duniter.org/t/liste-des-parametres-protocolaires-de-duniter-v2s/9297

Yes the constants api in JS is fine, I am already reading from it, looks like:

consts.universalDividend.udReevalPeriod.toNumber()

However some things I am unsure how to map. E.g.

• the units for durations, are they in seconds, milliseconds...?
• Things that are not constants, but state of the chain... like the monetary mass, number of members... where do I get them from?

Ah looks like units are sometimes blocks, sometimes millis... looking at the gdev.yaml file in duniter.

the units for durations, are they in seconds, milliseconds...?

It depends. You can look in the gdev.yaml as you wrote, or in the code because the generated documentation is being rewritten: nodes/rust/duniter-v2s!254 (merged)

Things that are not constants, but state of the chain... like the monetary mass, number of members... where do I get them from?

It it's chain state, then you'll have to look at a given block!

# something like that
# ↓ API       ↓ latest block    ↓ storage key
api.storage().at_latest().fetch(&gdev::storage().universal_dividend().monetary_mass())

It's like a key/value map, but instead of depending on the runtime it depends on the current block. But we have to add this to the duniter-squid indexer as well. Feel free to add an issue (https://git.duniter.org/nodes/duniter-squid/-/issues) so that @poka or I add the history of the monetary mass and member count.

You can also use the following query on a squid hasura endpoint like https://hasura.gdev.coinduf.eu/v1/graphql:

query UD {
  universalDividend(limit:1, orderBy: {blockNumber: DESC}) {
    monetaryMass
  }
}

{
  "data": {
    "universalDividend": [
      {
        "monetaryMass": 315262278536
      }
    ]
  }
}

But indexer should be used only for what can not be read directly from the blockchain.

Thanks @HugoTrentesaux this is very helpful

This seems to work:

    const monetaryMass = await api.query.universalDividend.monetaryMass();

Another question, how do we compute growth? Current growth and Theoretical growth target?

Theoretical growth target

This is c and in the code you have c²: SquareMoneyGrowthRate.

Current growth

I do not know on which timescale this growth is computed, you can look in Cesium v1 code or just omit this for now.

Also, we did refac the documentation and it is know available at https://doc-duniter-org.ipns.pagu.re/pallet_universal_dividend/pallet/trait.Config.html#associatedtype.SquareMoneyGrowthRate

mentioned in issue nodes/rust/duniter-v2s#240 (closed)

Fixed in 1ebdcd1e, thanks @txels!

I will open a new issue for web of trust panel which appears on the right in the initial screenshot

closed

mentioned in issue #23 (closed)