/biz/ - Business & Finance

>>18980316
>>18980303

Literal faggots

Are soijaks the perfect counterargument to every single thing in existence? You can't make this shit up. it literally never fails

>be 5 days and 8 hours from now
>BTC halves it’s reward
>Miners capitulating
>We did it, Reddit

>>18262894
>bought all the shit meme tokens
>holds ETH
checks out

>>18015069
>The dems literally want to give you more and not give to corps

>>17807736
>>17807737
>>17807742
>>17807745
midwit reddit infestation

>>16727627
you too reddit, KYS

>>16499992
>Whoosh I guess.
opinion discarded, u have to go back.

>>16405190
>>16405261
>>16405883
>>16406383
yes, I know why you don't want anyone to talk about tezos.
>>16406988
https://www.reddit.com/r/tezos/comments/dlnouv/we_were_not_ready_for_babylon_and_babylon_was_not/
>we were not ready for Babylon, and Babylon was not ready for us
>There have been at least three new bugs found in Babylon since it became active just a few days ago.
>When Babylon first became active, nodes didn't know how to handle the operations in the mempool that were using the Athens format. This caused connectivity issues on the network for a few hours after the transition until a hotpatch could be released and bakers updated their nodes.
>Transferring from a KT1 account now expects to receive the amount in mutez instead of tz. 100000 mutez = 1 tz. See GitLab bug report here.
The Babylon code uses integer division when calculating the block rewards, so a block that is missing only one endorsement receives as much reward as a block missing 16 endorsements.
>This means everyone is earning less than expected from baking rewards until this is fixed. The first mention I saw of this was shortly before Babylon activated, but it didn't get much of a response.

>This brings a few questions to mind:
>How is it that these bugs passed code review before even being submitted to the Tezos governance process? I.e. how come they were not caught through unit testing or other means of verifying the code was well written?
>How is it that these bugs were not discovered during testing phase? Did anyone actually test anything during testing phase? I feel some responsibility here because I didn't test anything.
If the testing phase didn't reveal these issues...

>>16401843
>>16401877
Nice

>>16399119
nice redditposting. when will you subhumans finally leave or kill yourselves?

>>16396500
decide for yourself anon
https://www.reddit.com/r/tezos/comments/dlnouv/we_were_not_ready_for_babylon_and_babylon_was_not/
>we were not ready for Babylon, and Babylon was not ready for us
>There have been at least three new bugs found in Babylon since it became active just a few days ago.
>When Babylon first became active, nodes didn't know how to handle the operations in the mempool that were using the Athens format. This caused connectivity issues on the network for a few hours after the transition until a hotpatch could be released and bakers updated their nodes.
>Transferring from a KT1 account now expects to receive the amount in mutez instead of tz. 100000 mutez = 1 tz. See GitLab bug report here.
The Babylon code uses integer division when calculating the block rewards, so a block that is missing only one endorsement receives as much reward as a block missing 16 endorsements.
>This means everyone is earning less than expected from baking rewards until this is fixed. The first mention I saw of this was shortly before Babylon activated, but it didn't get much of a response.

>This brings a few questions to mind:
>How is it that these bugs passed code review before even being submitted to the Tezos governance process? I.e. how come they were not caught through unit testing or other means of verifying the code was well written?
>How is it that these bugs were not discovered during testing phase? Did anyone actually test anything during testing phase? I feel some responsibility here because I didn't test anything.
If the testing phase didn't reveal these issues...

>>16394899
https://www.reddit.com/r/tezos/comments/dlnouv/we_were_not_ready_for_babylon_and_babylon_was_not/
>we were not ready for Babylon, and Babylon was not ready for us
>There have been at least three new bugs found in Babylon since it became active just a few days ago.
>When Babylon first became active, nodes didn't know how to handle the operations in the mempool that were using the Athens format. This caused connectivity issues on the network for a few hours after the transition until a hotpatch could be released and bakers updated their nodes.
>Transferring from a KT1 account now expects to receive the amount in mutez instead of tz. 100000 mutez = 1 tz. See GitLab bug report here.
The Babylon code uses integer division when calculating the block rewards, so a block that is missing only one endorsement receives as much reward as a block missing 16 endorsements.
>This means everyone is earning less than expected from baking rewards until this is fixed. The first mention I saw of this was shortly before Babylon activated, but it didn't get much of a response.

>This brings a few questions to mind:
>How is it that these bugs passed code review before even being submitted to the Tezos governance process? I.e. how come they were not caught through unit testing or other means of verifying the code was well written?
>How is it that these bugs were not discovered during testing phase? Did anyone actually test anything during testing phase? I feel some responsibility here because I didn't test anything.
If the testing phase didn't reveal these issues...

>>16390363

>>16388957
AHAHAHA WELL MEME'D FRIEND. UPBOATED

>>16387400
https://www.reddit.com/r/tezos/comments/dlnouv/we_were_not_ready_for_babylon_and_babylon_was_not/
>we were not ready for Babylon, and Babylon was not ready for us
>There have been at least three new bugs found in Babylon since it became active just a few days ago.
>When Babylon first became active, nodes didn't know how to handle the operations in the mempool that were using the Athens format. This caused connectivity issues on the network for a few hours after the transition until a hotpatch could be released and bakers updated their nodes.
>Transferring from a KT1 account now expects to receive the amount in mutez instead of tz. 100000 mutez = 1 tz. See GitLab bug report here.
The Babylon code uses integer division when calculating the block rewards, so a block that is missing only one endorsement receives as much reward as a block missing 16 endorsements.
>This means everyone is earning less than expected from baking rewards until this is fixed. The first mention I saw of this was shortly before Babylon activated, but it didn't get much of a response.

>This brings a few questions to mind:
>How is it that these bugs passed code review before even being submitted to the Tezos governance process? I.e. how come they were not caught through unit testing or other means of verifying the code was well written?
>How is it that these bugs were not discovered during testing phase? Did anyone actually test anything during testing phase? I feel some responsibility here because I didn't test anything.
If the testing phase didn't reveal these issues...

>>16373232
incompetent devs pushing bug riddled code live on a financial operating system with over a billion USD of other people's money on the line. Sorry reddit pajeet but these multiple-daily shitcon spam threads are gonna get called out every day.

https://www.reddit.com/r/tezos/comments/dlnouv/we_were_not_ready_for_babylon_and_babylon_was_not/
>We were not ready for Babylon, and Babylon was not ready for us
>There have been at least three new bugs found in Babylon since it became active just a few days ago.
>When Babylon first became active, nodes didn't know how to handle the operations in the mempool that were using the Athens format. This caused connectivity issues on the network for a few hours after the transition until a hotpatch could be released and bakers updated their nodes.
>Transferring from a KT1 account now expects to receive the amount in mutez instead of tz. 100000 mutez = 1 tz.
>The Babylon code uses integer division when calculating the block rewards, so a block that is missing only one endorsement receives as much reward as a block missing 16 endorsements.
>This means everyone is earning less than expected from baking rewards until this is fixed. The first mention I saw of this was shortly before Babylon activated, but it didn't get much of a response.
This brings a few questions to mind:
>How is it that these bugs passed code review before even being submitted to the Tezos governance process?
>I.e. how come they were not caught through unit testing or other means of verifying the code was well written?
>How is it that these bugs were not discovered during testing phase?
> Did anyone actually test anything during testing phase? I feel some responsibility here because I didn't test anything.
>If the testing phase didn't reveal these issues, what can we learn from this to make sure the testnet adequately simulates the new protocol on mainnet in the future?

>>16297035
>automatically thinks in terms of red team vs blue team

>>16164330
okay leddit

>>16137545
good goy

>>16059102
>>All I can say is this to me it's a sign of begining of the nationalization of Bitcoin/Cryptocurrency related infra in mainland
>>Eventually, all things can be state-owned, or at least partially (mining, ASIC, exchanges, wallets, etc etc)
yes goy, chose the one of the cryptos with the worst planned implementations of proof of stake

a tipping coin to send to friends and acquaintances whenever they signal their adherence to the core values of social justice and all that crap. finally get everlasting social justice score that you can show off to your friends and more importantly that you can post to your linkedin profile

>>15973914