substrate | Substrate : The platform for blockchain innovators | Blockchain library

I am still missing some parts of your code. But I have understood your goal. For this reason, I have written a general example to make it clear to you what you need to pay attention to in order to get your code to work.

1. Link your vote buttons to a click event.
2. Determine if it is an up / down vote when it fires.
3. Get the current count and recalculate the count. Important: parseInt()
4. the value you pull from the DOM to calculate it.
5. update the counting element

That's it!

You should pass {"withType": true} to the sign method too.

The formal documenation of StorageValue can be found here https://paritytech.github.io/substrate/monthly-2021-09+1/frame_support/storage/types/struct.StorageValue.html

There you can see that the third generic QueryKind is by default the type OptionQuery, when you don't provide a specific type, then OptionQuery is used.

In the method implementation of the type StorageValue you can see it requires some bounds on the generics https://paritytech.github.io/substrate/monthly-2021-09+1/frame_support/storage/types/struct.StorageValue.html#impl

Especially it requires QueryKind: QueryKindTrait, This means QueryKind must implement how the value is queried from storage.

There is currently 2 implementors: OptionQuery and ValueQuery: https://paritytech.github.io/substrate/monthly-2021-09+1/frame_support/storage/types/trait.QueryKindTrait.html#implementors

OptionQuery implement the trait in a way that returns None when no value is found in the storage. ValueQuery implement the trait in a way that returns some on empty value (configured by the generic OnEmpty) when no value is found in the storage.

So you would use either ValueQuery when you want to get some "default" value when you try to get some value from storage and there is no value, and OptionQuery when you want to get None, when you try to get some value from storage and there is no value.

The consequences are visible in the signature of the method: the method get will return either a value or an option: https://paritytech.github.io/substrate/monthly-2021-09+1/frame_support/storage/types/struct.StorageValue.html#method.get

Here how I dit it:

For example: pallet BoTrading need to call get_suitable_lp on pallet BoLiquidity

pallets/BoLiquidity/src/lib.rs

I got an answer substrate-validator-set. If you want to dynamically add validator on a PoA network, you need to add a session pallet, and let session to manage the auro key and grandpa key.

Accounts are just public keys in the node template. This means you can check every possible public key and it will return zero. But that doesn't mean that there is any state associated to this account. (assuming you have configured an existential deposit above 0).

If you want to add accounts on genesis, just check out the testnet_genesis. The endowed_accounts(4th argument) is what you are searching for. These are the accounts that get some balance at genesis. All of this code is chain depended and you can change it as you like.

T is a generic type which represents the entire Runtime configuration for your chain.

Substrate is designed to be modular and configurable, and thus we allow every pallet to be completely configured for your needs.

A simple example of this is that we make no assumptions about what type you use for the block number for your chain. Throughout the code, the block number type is generic, and can be referenced by the T::Number type.

At some point, that generic type needs to be concretely defined, which happens in the runtime configuration. This T generic type is passed to all pallets in order to share what those concrete types actually are, and make everything work in the end.

Check out this repository for a helpful example of how you can transition to concrete types into generic types, and then it will be obvious how the T syntax came to be:

https://www.youtube.com/watch?v=6cp10jVWNl4

https://github.com/shawntabrizi/substrate-trait-tutorial

One option to achieve your desired result:

1. Set clip="off" in coord_cartesian`
2. Make some room for the labels by increasing the bottom margin of the title
3. Set y=1.05 for the labels (the max of data range + the default expansion of the scale by .05)
4. Set min.segment.length=0
5. Increase the ylim for the labels
6. Nudge the position of the labels

Note: Getting your desired result you probably have to fiddle around with the values for the nudging, the ylim and the margin.

Can I just send tokens to a public key that never been seen on the network?

Yes. If you use AccountId32 as account id, every account is just a 32 byte long public key.

Even when an account falls below existential deposit, the account "stays", only all associated data is reaped. Next time you send funds to this account, it will be usable again.