Epoch 0 payouts have been sent

9 blocks have been produced this epoch.

As a reminder, you can find all payouts in realtime on this page :

• Payouts

On June, 4th the mina Blockchain has undergone its biggest upgrade ao far.
This impacted the payout timeline for several reasons.
The first one is that we were asked by the Mina foundation to delay the payouts for epoch 78 until the Hardfork happened.

Epoch 78 ended around 4AM on June, 4th a few hours before the upgrade process begun.
Right after the Epoch 78 ended, the epoch 79 started on the old chain.
This epoch 79 lasted only a few slots/blocks until we reached the transaction stop slot at June 4th, 9AM UTC that started the upgrade process.

We are now on the new chain.
This new chain started again from Epoch 0 !! This is a bit like a reborn of the Mina Blockchain !!

Time for everyone to ugrade and ensure everything is ok was the main reason to delay the payouts.
I was also asked personnaly by the Mina Foundation to delay my payouts a bit in order to perform some validation tests.

At this time (June 07th), I am still waiting the Go from the mina fundation to trigger my payouts for both epoch 78 and 79.
Once I get the go, I will immediately trigger the payout for both epochs.

In conclusion, no need to worry about the payouts !! They are coming !!

In order for you to know what you can expect for these two epochs, you'll find the details of the due payouts below for each 78, 79 epoch.

EXPECTED EPOCH 78 PAYOUTS

(index)	publicKey	amountMina	feeMina	memo
0	'B62qiburnzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzmp7r7UN6X'	5040	0.001	'0e90b06c189551afc6ba1242df347726'
1	'B62qoUVTKseKucekfhegBxuaMkoJ37ThTE12gpGWjExV4UZvhqZD6w9'	2623.521650407	0.001	'0e90b06c189551afc6ba1242df347726'
2	'B62qimKm1pqwrR9yYBrdPVS8Cb3PU3RV9pd4gzBk9qyxtYUuxFGdovf'	1887.895009532	0.001	'0e90b06c189551afc6ba1242df347726'
3	'B62qnBCeHSLmPzDvM4aceJ9VgsKx1qV2V4Z9EamYCWAkjSPufgEEBx8'	89.067717079	0.001	'Naamah#8064_epoch78_payout'
4	'B62qp9iEXdtQNK97cLYsJQ1HbsKuHs3QUBSiU5PVgTzXkHcJi4VNDpH'	19.374223594	0.001	'Naamah#8064_epoch78_payout'
5	'B62qqtrL12wX6GFmBAM2NrJjDMiyHa7xogQo27eTNojEmXV1V1XdqXe'	16.08477667	0.001	'Naamah#8064_epoch78_payout'
6	'B62qntF3qLMs6tqJzT7bpJwSWY61LoUokoUoqfiQrQEeLaJbdWfT9xc'	5.056818142	0.001	'Naamah#8064_epoch78_payout'
7	'B62qmATRJ1ZJ9VmjpMbqGfamQ5ZykCJktPJTJkGuec5i4j3Sgbe5rsB'	3.146624633	0.001	'Naamah#8064_epoch78_payout'
8	'B62qp4pGCsKJxoBWoKfTefdge8zZ1B4iZWENP7iLNHrBpQwnSDYrz3d'	3.05887009	0.001	'Naamah#8064_epoch78_payout'
9	'B62qnPd3ZjQB6TJLqpcEm5H2CBJw48nuKJRkRfKcTx7CTTZwoN8YbTN'	3.050289531	0.001	'Naamah#8064_epoch78_payout'
10	'B62qp8nAcGNbrBtdoEjfzM17A7yvgdiwqEaBbq6hxCtwnmYpbZfaPiV'	1.521624799	0.001	'Naamah#8064_epoch78_payout'
11	'B62qqm8gJ14JUJpkWySZcTHJiLyFUXCKYvk3PHDu3iDgzczLkAXBDv4'	0.775769963	0.001	'Naamah#8064_epoch78_payout'
12	'B62qkbhoBDynDW2nGVqbh3njBHzV17iaWs7c7X56MeEjQdMZ424gUtF'	0.495638432	0.001	'Naamah#8064_epoch78_payout'
13	'B62qq1q9GTbS7AqD4PhrCfS1QiLnahGE1jH9ZbttQ5TK9QAFjBh98yj'	0.035971795	0.001	'Naamah#8064_epoch78_payout'
14	'B62qq9ZvAwR3feAwFzuPsbfBMUUB18MpWHd7Hy9uN3GJgu3bW9FoaPV'	0.014836233	0.001	'Naamah#8064_epoch78_payout'
15	'B62qmtcbMEVVKN2guoyVEqmiPZtbvNhz4VUvUYvxesya3WHPkLiBvdK'	0.010165582	0.001	'0e90b06c189551afc6ba1242df347726'

EXPECTED EPOCH 79 PAYOUTS

(index)	publicKey	amountMina	feeMina	memo
0	'B62qiburnzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzmp7r7UN6X'	720	0.001	'0e90b06c189551afc6ba1242df347726'
1	'B62qoUVTKseKucekfhegBxuaMkoJ37ThTE12gpGWjExV4UZvhqZD6w9'	373.555704332	0.001	'0e90b06c189551afc6ba1242df347726'
2	'B62qimKm1pqwrR9yYBrdPVS8Cb3PU3RV9pd4gzBk9qyxtYUuxFGdovf'	269.633191796	0.001	'0e90b06c189551afc6ba1242df347726'
3	'B62qnBCeHSLmPzDvM4aceJ9VgsKx1qV2V4Z9EamYCWAkjSPufgEEBx8'	12.485362447	0.001	'Naamah#8064_epoch79_payout'
4	'B62qqtrL12wX6GFmBAM2NrJjDMiyHa7xogQo27eTNojEmXV1V1XdqXe'	3.697952496	0.001	'Naamah#8064_epoch79_payout'
5	'B62qp9iEXdtQNK97cLYsJQ1HbsKuHs3QUBSiU5PVgTzXkHcJi4VNDpH'	2.715842888	0.001	'Naamah#8064_epoch79_payout'
6	'B62qntF3qLMs6tqJzT7bpJwSWY61LoUokoUoqfiQrQEeLaJbdWfT9xc'	0.706490137	0.001	'Naamah#8064_epoch79_payout'
7	'B62qmATRJ1ZJ9VmjpMbqGfamQ5ZykCJktPJTJkGuec5i4j3Sgbe5rsB'	0.440989712	0.001	'Naamah#8064_epoch79_payout'
8	'B62qp4pGCsKJxoBWoKfTefdge8zZ1B4iZWENP7iLNHrBpQwnSDYrz3d'	0.428785393	0.001	'Naamah#8064_epoch79_payout'
9	'B62qnPd3ZjQB6TJLqpcEm5H2CBJw48nuKJRkRfKcTx7CTTZwoN8YbTN'	0.426210676	0.001	'Naamah#8064_epoch79_payout'
10	'B62qp8nAcGNbrBtdoEjfzM17A7yvgdiwqEaBbq6hxCtwnmYpbZfaPiV'	0.213297216	0.001	'Naamah#8064_epoch79_payout'
11	'B62qqm8gJ14JUJpkWySZcTHJiLyFUXCKYvk3PHDu3iDgzczLkAXBDv4'	0.108746192	0.001	'Naamah#8064_epoch79_payout'
12	'B62qkbhoBDynDW2nGVqbh3njBHzV17iaWs7c7X56MeEjQdMZ424gUtF'	0.069476295	0.001	'Naamah#8064_epoch79_payout'
13	'B62qq1q9GTbS7AqD4PhrCfS1QiLnahGE1jH9ZbttQ5TK9QAFjBh98yj'	0.005041044	0.001	'Naamah#8064_epoch79_payout'
14	'B62qq9ZvAwR3feAwFzuPsbfBMUUB18MpWHd7Hy9uN3GJgu3bW9FoaPV'	0.002072776	0.001	'Naamah#8064_epoch79_payout'

On June, 4th the mina Blockchain will undergo its biggest upgrade ao far.

This update will bring the ZK programmability layer to the blockchain and ending the supercharged rewards.

In the same time several potential impacts should be expected.

D-Day Timeline

The progress of the upgrade and the timeline are documented here:

https://minaprotocol.com/blog/minas-berkeley-upgrade-what-to-expect

and here

https://minaprotocol.com/mainnet-upgrade-status

The Block producer timeline

Every block producer will have to update their nodes in order to ensure the resume of the upgraded Blockchain.

Here is a simplified overview of the tasks that every block producer will have to achieve on June, 4th.

Before June, 4th

The only action required by block producer is to update their nodes to version 2.0.0. (All my nodes are upgraded already obviously !)

On June, 4th

• STEP 1

No specific action is required until the stop network slot is reached (14:00 UTC). At least one node must still be active and connected to the network until the stop slot is reached (ideally, all nodes of an operator can remain online). The calculation of uptime will be taken into account until the stop slot is reached (14:00 UTC).

• STEP 2

Until the upgrade package is released (20:00 UTC): No action required.

• STEP 3

Once the upgrade package is available: All operators update and restart their nodes (20:00 UTC - 00:00 UTC). Uptime calculation will resume at 00:01 UTC with a tolerance until 01:01 UTC.

• STEP 4

From 00:00 UTC, the blockchain will restart on Berkeley fully operational: block production, snarks production, uptime, ...

What's next ?

After the Hard Fork (if all goes well):

• The end of supercharged blocks will result in a decrease in profitability but will also level the playing field for all serious validators. It will also reduce the number of new tokens created, which will limit the inflationary nature of the token (and that's a good thing).

• As a delegator, it will be important to ensure that your validator is up-to-date with their nodes from now on (version 2.0.0) until the update is triggered and their validation nodes are updated, otherwise, they will operate a zombie chain that will no longer produce valid rewards (for you). I encourage everyone to contact their validator to ensure they are up-to-date and that everything is in order for the update on 06/04.

Finally, there will certainly be impacts on tools, explorers, and websites concerning Mina. Some blockchain explorers may experience disruptions or become non-functional or display inconsistent information. Other services will be completely stopped (e.g., Mina Explorer's GraphQL APIs), which may also cause interruptions to some services that use them (my site, for example, uses the Mina Explorer GraphQL API, which I will have to replace eventually to display produced blocks, delegations, and payouts).

In summary, be patient, do not hesitate to contact your validator if you have any questions or problems, and do not panic if the rewards for the epoch post-hard fork take a little time to arrive 😉

This update is going to be epic. It is important to realize the amount of work and investment that goes into not only updating but also synchronizing all the actors, which are ultimately the key to the success of updating a fully decentralized application.