atxs: changes related to poet ticks

[dshulyak]

the weight of the atx computed from tick count multiplied by the number of units. tick height of the atx computed from base tick height plus tick count. base tick height is a tick height of the positioning atx. tick count is a number of leaves in the poet proof divided by tick size. tick size is a protocol parameter, meant to kept the size of the weight in uint64 bounds.

positioning atx is an atx with the highest tick height from the last epoch.

[dshulyak]

the verify flow is not intuitive. i'd prefer to move things around and make sure once the ID is set, the tick height is also recorded.

id needs to be computed earlier, in order to check data in the database. ticks can be recorded only after validation i will check if i can shift that around in a way that allows to bypass expensive validation, but likely it won't be possible

is it possible to combine the API for base tick height and tick count into just tick height?

base tick height is used for proposals tick count is used for weight computation

[dshulyak]

bors try

[bors[bot]]

try

Build succeeded:

• ci-stage2

[dshulyak]

bors merge

[bors[bot]]

Pull request successfully merged into develop.

Build succeeded:

• ci-stage2