I found more information here: There might be a fork...

It seems that they forget to give some operations proper size information -> some ops are free to spam. As they have no size, they can be broadcasted from an account with zero BLURT and zero BLURT Power.

I found the problem: witness_set_properties has no size property.

It seems to be caused by EIDOS:

I like to write my markdown posts with an external editor. visual studio code and typora are great for this. Beempy post is very comfortable as it broadcast the markdown to HIVE and also uploads all images

That's right, I was just surprised about the amount. Why are 96.25 % of all EOS ops a transfers of 0.0001 EOS without memo?

Could be, but the transactions are meaningless, they are just sending 0.0001 EOS without memo. Why sending 90 times 0.0001 EOS to the same account instead 0.0090 EOS once?

Sorry, I messed up by changing the post title. The correct post can be found here:

I think it is the official account, as eosio.token does not need to have any CPU or NET staked:

You are right, I changed the title to EOS inflates ...

The random number generation for hive-engine is defined here: const rng = seedrandom(`${prevRefHiveBlockId}${refHiveBlockId}${transactionId}`); the random number function is using rng: The mining source

Yes this works also. Do you know when the update is applied to all API full nodes?

Thanks for your work, it helped me to add this feature to beem. At the moment it is only used on from beem import Hive from beem.account import Account hive = Hive(" account =

It seems that they need to backup BTC 1:1

Thanks for pinging me, I finally found and fixed the problem and improved the code. rewarding should run smooth again.

It exists and works. have a look here:

They just count how often a security report is fetched and an update check is performed. Both are done once when tails is booting. So I would not call this spying (both calls are made through tor, so IP

In september 2020, Tails has been started more than 906 004 times (30 200 boots a day on average). source

Yes there is a service from arcange:

Yes, I fixed everything and the rewarding.app is working.