Hive SQL - Hardfork 26 support

avatar
(Edited)

The hardfork 26 (codename Evolution) has been activated a few days ago as all top 20 witnesses are now running the v1.26 code on their nodes (see here).

My API servers have also been upgraded to the new code and are now providing HiveSQL with new data.

Thanks to the mirrornet, I have been able to prepare HiveSQL to fully support the new (virtual) operations now available with this new version.

What's new?

While no new operations were added during this hardfork, this is not the case for virtual operations.

As a reminder, Virtual Operations are operations resulting from the activity on the blockchain but, unlike classic operations, they are not initiated by users.

And since hardfork 26, no less than 7 additional Virtual Operations are now available to better monitor what is happening in the blockchain.

New tables

  • VOCollateralizedConvertImmediateConversion
ColumnDescription
ownerThe account requesting the conversion
requestidThe request identifier
hbd_outAmount of HBD sent to the account

This virtual operation is triggered after a collateralized_convert operation is issued to convert HIVE to HBD.

Half of the HIVE amount is converted immediately into HBD (using the minimum witnesses price feed for the last 3.5 days) and sent to the owner.

  • VODHFConversions
ColumnDescription
treasuryThe account of the DHF
hive_amount_inThe amount of HIVE to convert
hbd_amount_outThe amount of HBD generated

When a user transfer HIVE to the DHF account (hive.fund), the amount is immediately converted to HBD and this virtual operation is generated.

This virtual operation is also generated during block processing every day during daily proposal maintenance.

Note: a portion of the HIVE on the treasury balance is converted to HBD and thus increases the funds available for proposals.

  • VODHFFundings
ColumnDescription
treasuryThe account of the DHF
additional_fundsThe amount of HIVE to convert
additional_funds_symbolHBD

This virtual operation is generated during block processing every proposal maintenance period.

Note: while the DHF receives part of inflation every block, this virtual operation is generated only when there are proposal payouts.

  • VOHardforks
ColumnDescription
hardfork_idHardfork number

This virtual operation is generated during block processing every time new hardfork is activated.

  • VOLimitOrderCancelleds
ColumnDescription
sellerThe account who created the order
amount_backThe amount of the cancelled order
additional_funds_symbolHIVE or HBD

This virtual operation is generated every time an existing limit order is canceled. It happens on explicit call (first operation), or in the rare case of filling a limit order (second or third operation) when, after filling most of it, the remaining funds are too small (they would round to zero when sold).

This virtual operation is also generated during block processing for orders that reached their expiration time without being filled.

  • VOPowRewards
ColumnDescription
workeraccount mining a block
rewardamount received
reward_symbolHIVE

This virtual operation occurs each time a block is produced. It contains the rewards that are given to witnesses (and previously miners) for their work.

  • VOProducerMisseds
ColumnDescription
producerName of the witness who missed a block

This virtual operation is generated during block processing when a witness failed to produce his block on time.

  • VOProposalFees
ColumnDescription
creatorAccount creating a proposal
treasuryThe account of the DHF
proposal_idThe proposal identifier
feeThe amount paid for creating the proposal
fee_symbolHBD

This virtual operation is generated every time an account creates a new proposal.


Note: Many of the above mentioned table may currently only contains no records or only records from hardfork 26 and later. It is planned to perform a replay of the blockchain to re-inject data relating to previous events.

Documentation

HiveSQL documentation has been updated and can be viewed at https://docs.hivesql.io

Support

If you have any questions or remarks, support is provided on the HiveSQL Discord Channel.

Thank you.


Check out my apps and services


Vote for me as a witness



0
0
0.000
18 comments
avatar

pixresteemer_incognito_angel_mini.png
Bang, I did it again... I just rehived your post!
Week 127 of my contest just started...you can now check the winners of the previous week!
!PIZZA
6

0
0
0.000
avatar

Thanks for this awesome information.

0
0
0.000
avatar

I am curious about the HBD conversion processes, as I have not well understood how that occurs. Can you point me to a source that could edify me regarding conversions to and from HBD, please?

I am glad you continue to provide your excellent services on Hive. Few do more to educate me on how Hive works.

Thanks!

0
0
0.000
avatar

The hardfork 26 (codename Evolution) has been activated a few days ago as all top 20 witnesses are now running the v1.26 code on their nodes (see here).

When i saw this i became very happy, This new update will really change many things in the Blockchain.

0
0
0.000
avatar

YEs, this hardfork is a major "Evolution"

0
0
0.000
avatar

Evolution is what we need in the world

0
0
0.000
avatar

This HF feels surreal, everything is so smooth and fast.

0
0
0.000
avatar

It's funny to read your comment because all of Hive's hardfork ran smoothly.
Apparently, we are all still traumatized by our terrible past experience with Steem 😂

0
0
0.000
avatar

Yeah, you're right the trauma is still there. But it's also notable how fast voting has become.

0
0
0.000