[00:35:31] 82e2b0a3fdcf71e19102f106a26d42a6389a12eaa084242933dd0f97702b0538 navcoin-4.7.0-aarch64-linux-gnu.tar.gz 73635ba42785f06f26171783ed4ee63c224d8c1e5cfe208085ffbb2ad25530c7 navcoin-4.7.0-arm-linux-gnueabihf.tar.gz a916cfce8c07b8d023c68f127f51c4c46194a2661ae062593a7518d7133e3479 navcoin-4.7.0-i686-pc-linux-gnu.tar.gz 39a6c4246edda043bb5982761c1c5234e849cf24b930d2bd3d3fc45b59aed0ec navcoin-4.7.0-osx-unsigned.dmg [00:35:32] 803c0fe70d9d7422ceb62550cae16c502840200c1f6f2995dfdf332eecdb4900 navcoin-4.7.0-osx-unsigned.tar.gz ba7e3b70e918fe3e3c020482ced1f35d80ad8972f32fac913e46953d61b6f17c navcoin-4.7.0-osx64.tar.gz 816ab35b6f58aec21c1db1924850c87856163c5cb5c922b4554cf1ccbdf113df navcoin-4.7.0-riscv64-linux-gnu.tar.gz 99c8a76b982cb6765ff0e91ecb4217e016127a529d1328e71300ca60e9a5d21a navcoin-4.7.0-win32-setup-unsigned.exe [00:35:33] a2a92eda91ed4efffdb5c66d4d7dc676ed70c8fbc22d57ad185178daacf80aa2 navcoin-4.7.0-win32.zip 46116c9ca2e240eecf3ae439b4e8424b1bfbb958c8564d12cf67e29b4e1c2e02 navcoin-4.7.0-win64-setup-unsigned.exe a770f0eeed1672c2db07653243db14126600011ea671dac5526500ca4d3caa92 navcoin-4.7.0-win64.zip 05e0c5970478c03805110f4b04eb511a47d600379d3a39b53d77e7557b95288c navcoin-4.7.0-x86_64-linux-gnu.tar.gz [00:35:33] e89975b3e2e6c90d46f4a5d05d4ae7ccf9e16ed09317b3d0a02d628d0faeeaa5 navcoin-4.7.0.tar.gz [00:35:57] so i got the same as salmon it looks like [00:36:26] afaik for the build script you can pass in a branch, commit hash or tag [00:37:00] so i was just pointing it to the tag '4.7.0' but commit hash or even just 'master' should work at the moment as long as nothing else has merged to master [00:37:26] i ran master [02:26:26] lets get one more positive hash check [02:26:28] then we'll launch it [04:29:33] I used 4.7.0 tag, not sure why I got a different hash, my PC must have a ghost, lol. [17:09:57] there are quite a few [22:05:40] anyway @miuno having a max reorg depth is a bad design decision as it prevents nodes from reorg'ing to the right chain in extreme cases [22:13:56] true, but if the tradeoff is leaving the chain completely insecure, some might take it [22:14:46] it's just a bandaid on an imperfect fix - it'd be better to look for another antispam solution [22:22:40] from my point of view, ideally, the whole utxo-based proof of stake thing that many projects are using should be redesigned. reusing bitcoin's architecture for a different consensus model has proven to be imperfect [22:24:14] lol, bitcoin architecture is not the problem, it's the shitty consensus [22:27:51] well, if you are blindly against proof of stake then there's not much to talk about [22:31:21] it's not that. if you can show one that work, we're fine. the problem is you can't and you are ok to risk people's money in what you know is crazy insecure. [22:33:21] i'm not a pos maximalist - proof of work is good for initial coin distribution and to secure big chains with unique algos [22:33:49] for smaller chains, which are legitimate to exist, is not a valid solution [22:36:01] if you did market it honestly, no one would be here. insecure chain is not legitimate. i think our views are too far away [22:36:35] i'm gonna leave you in that, not going to support this craziness [22:37:28] it's just a healthy conversation, i don't see any craziness [22:41:10] @miuno https://mobile.twitter.com/vitalikbuterin/status/1077548790272405504 [22:41:35] https://twitter.com/vitalikbuterin/status/1077548790272405504 [22:42:54] @miuno Is Vitalik crazy? [22:43:12] @Goku https://mobile.twitter.com/hodlonaut/status/1077549267550724096 whats your point? [22:44:07] I don't know hodlonaut... Something special from him [22:44:26] being threatened by faketoshi [22:44:38] Vitalik is just another dishonest devwho wants to fill his pocket [22:44:49] Ah yes... This story I know @aguycalled [22:45:13] you are listening to fake gods, i'll leave you there, bye [22:45:43] 👋 [23:56:32] @miuno Your message would be valued a lot more if it was constructive. Your rant takes the whole value out of the message unfortunately.