2018-10-17 04:06:06
*https://github.com/snowblossomcoin/channels/compare/f5a1c5e8204d...1e058aac30a5*
https://github.com/snowblossomcoin/channels/commit/1e058aac30a5066e7bc22bf004cce03eb1c535d2 - DHT in progress
GitHub
2018-10-17 05:19:43
*https://github.com/snowblossomcoin/snowblossom/compare/00890ea39b74...dc9a3ea017b3*
https://github.com/snowblossomcoin/snowblossom/commit/dc9a3ea017b3a6e36e1b4679cb60a703b73de5ec - Add getClose keys to protomap
GitHub
2018-10-17 05:52:28
*https://github.com/snowblossomcoin/channels/compare/1e058aac30a5...0759a49286c1*
https://github.com/snowblossomcoin/channels/commit/0759a49286c1d1baef2a11e6083c61ea23a748c2 - DHT in progress
GitHub
2018-10-17 14:10:31
Is there any way to grab the circulating supply through the RPC?
Eric
2018-10-17 14:11:25
We're conceptualizing a system that automatically freezes deposits based on network variables. Supply going up substantially faster than expected is probably caused by some bug (such as bitcoin's duplicate input bug)
Eric
2018-10-17 14:11:44
Might also be a nice thing for the explorer to show
Eric
2018-10-17 14:56:22
not sure what sort of clown college you think this is, but ok
Fireduck
2018-10-17 14:56:29
so that would look like sum of utxo?
Fireduck
2018-10-17 15:04:53
Lol clown college sounds like a great horror movie theme
Eric
2018-10-17 15:05:00
Yea. Probably a running total of utxos
Eric
2018-10-17 15:06:59
clown college: you won't be laughing soon
Fireduck
2018-10-17 15:07:54
The trouble with tracking the utxo sum is that any code that did it incrementally per block would be perhaps subject to the same hypothetical bug so the safe thing to do is enumerate and sum the values of the entire db
Fireduck
2018-10-17 15:08:22
which wouldn't be too bad, but not something you want to do on the fly
Fireduck
2018-10-17 15:08:55
I could make a tool that does that on an existing database
Fireduck
2018-10-17 15:09:11
or actually,
Fireduck
2018-10-17 15:09:23
could do it via queries to an existing node
Fireduck
2018-10-17 15:09:38
since the get utxo code will already support that use case just fine
Fireduck
2018-10-17 15:21:07
We would ideally check it every block or every few minutes - so performance could be an issue as the blockchain grows. AFAIK the bugs we've dodged would have been caught by the incremental counter - VEO's integer underflow, bitcoin's dupe input. I suppose most ideal would be to have both and run the full sum occasionally
Eric
2018-10-17 15:30:22
actually, you can just run the richlist program and sum the outputs
Fireduck
2018-10-17 15:33:43
nevermind, this was written by an insane person
Fireduck
2018-10-17 15:33:52
it is actually reading each block for some insane reason
Fireduck
2018-10-17 15:36:36
Should get sum of unspent, number of outputs, number of addresses, etc.
Should also replace that damn fool richlist implementation.
GitHub
2018-10-17 15:36:40
@Eric https://github.com/snowblossomcoin/snowblossom/issues/127 Should get sum of unspent, number of outputs, number of addresses, etc.
Should also replace that damn fool richlist implementation.
Fireduck
2018-10-17 15:48:17
Cheers, thanks
Eric
2018-10-17 18:46:11
*https://github.com/snowblossomcoin/snowblossom/compare/dc9a3ea017b3...a57ea29e3be6*
https://github.com/snowblossomcoin/snowblossom/commit/a57ea29e3be6faf176fb88d88fd6001bec9998ec - fix get closest
GitHub
2018-10-17 21:51:46
@Eric if anyone's doing something like that, it should be very easy to spot.
Clueless
2018-10-17 21:55:44
If someone is awake and paying attention
Fireduck
2018-10-17 21:55:56
sounds like they are trying to build something to catch it if those things aren't true
Fireduck
2018-10-17 21:56:15
I was actually doing that myself last night.
Clueless