2018-06-09 05:31:04
*https://github.com/snowblossomcoin/snowblossom/compare/d1beca135ceb...2c036951892b*
https://github.com/snowblossomcoin/snowblossom/commit/2c036951892b1a65af2f3f9befbff670c6d84104 - Preparing 1.0.6 release
GitHub
2018-06-09 05:55:34
*https://github.com/snowblossomcoin/snowblossom/compare/2c036951892b...1b03d0b79d81*
https://github.com/snowblossomcoin/snowblossom/commit/1b03d0b79d81c03428d18a61d5e75a44d241d658 - Updating windows readme
GitHub
2018-06-09 05:57:33
[snowblossomcoin/snowblossom] Release - 1.0.6 - pooled mining
GitHub
2018-06-09 06:14:58
@bl0ckchain can I use those arts you uploaded?
Fireduck
2018-06-09 06:25:21
Does the 1.0.6 release have improvements for linux too? Afaik it’s only small changes and some for windows
bottob88
2018-06-09 06:25:44
*https://github.com/snowblossomcoin/snowblossom/compare/1b03d0b79d81...3aec9ddb84c8*
https://github.com/snowblossomcoin/snowblossom/commit/3aec9ddb84c81d35a034b5ccdb34e6161193e0cf - Adding icon
GitHub
2018-06-09 06:26:43
@bottob88 yeah, nothing much in 1.0.6. Mostly just packaging in PoolMiner
Fireduck
2018-06-09 06:29:09
@bl0ckchain I did weird shit to it, I hope you can forgive me
Fireduck
2018-06-09 09:30:27
no problem you make what you want with it :slightly_smiling_face:
bl0ckchain
2018-06-09 09:52:18
favicon on the explorer look good :wink:
bl0ckchain
2018-06-09 17:49:44
I'm thinking the best way to make a decent explorer is to have something that is running and pumping all the data into a SQL database and then host a website off the SQL database
Tyler Boone
2018-06-09 17:50:42
Maybe. At Bitcoin scale that doesn't work very well, at least not with MySQL
Fireduck
2018-06-09 17:51:45
If you need other data views you can stub them out and tell me to write them
Fireduck
2018-06-09 17:52:06
@Tyler Boone Databases are usually more for complex and large lookups and referencing and such.
Clueless
2018-06-09 17:52:25
These blockchains to some referencing, but it's mostly static.
Clueless
2018-06-09 17:52:47
It'd be best to do some sort of direct IO based recording in a determinisitic fashion?
Clueless
2018-06-09 17:53:08
Lower the database overhead, ram requirement, and do lookups basically as needed (for an explorer)
Clueless
2018-06-09 17:53:27
it depends on what you want the explorer to do
Tyler Boone
2018-06-09 17:53:43
for example, how can I list all outgoing transactions from an address?
Tyler Boone
2018-06-09 17:53:47
maybe it's possible with the trie
Tyler Boone
2018-06-09 17:53:56
but if not, then you have to iterate the entire blockchain
Tyler Boone
2018-06-09 17:54:10
We're not trying to cross reference, **give me all the >20 age, green eyed, people that liked milk, and show them all the ads for egg related products**
Clueless
2018-06-09 17:55:04
I think you'd build an address index
Clueless
2018-06-09 17:55:11
yes, but we are trying to serve views of data quickly and at minimal expense
Tyler Boone
2018-06-09 17:56:02
"build an address index". build that in what?
Tyler Boone
2018-06-09 17:56:54
I'm advising against a database , because they have tons of overhead aimed at tons of overkill procedures we don't need.
Clueless
2018-06-09 17:57:23
We need an address history index for like clients anyways I plan on making it
Fireduck
2018-06-09 17:57:45
We're interested in just the referencing.
For each block, index each transaction, index the the amount in address, reference list of transactions to addresses
Clueless
2018-06-09 17:58:43
@Fireduck Sweet, so if you make the framework for clients to go back, 10-100 blocks, we could just extend that to nodes or explorer to do it for the entire chain.
Clueless
2018-06-09 17:59:44
if the trie contains the data and a way to traverse it, then a client would request just the trie nodes needed.
Tyler Boone
2018-06-09 17:59:46
*we* lel
Clueless
2018-06-09 18:00:01
I don't know how that works. :P
Clueless
2018-06-09 18:00:15
Trie is only utxo
Fireduck
2018-06-09 18:00:30
OK, well that answers that
Tyler Boone
2018-06-09 18:00:32
Need separate address history
Fireduck
2018-06-09 18:00:43
I think a simple address index would do nicely
Clueless
2018-06-09 18:00:48
We just limit the size for the application.
Clueless
2018-06-09 18:01:50
Clients need last 10 blocks to see they received a payment, from a person at time, whatever.
Nodes need last 1000 blocks worth, because a family might collectively review payments.
Explorer stores entire chain's worth of index.
Clueless
2018-06-09 18:02:19
but I don't actually know. >.>
Clueless
2018-06-09 18:18:00
@Fireduck, in snowblossom.proto TransactionInner has a CoinbaseExtras, but the class generated from that (TransactionInner) doesn't have it. am I insane?
Tyler Boone
2018-06-09 18:19:00
I am insane
Tyler Boone
2018-06-09 18:19:04
it's there
Tyler Boone
2018-06-09 18:20:17
Yep
Fireduck
2018-06-09 18:20:41
I plan on making address_idx an optional node option like tx_index
Fireduck
2018-06-09 18:20:43
I was mistyping because I'm on my laptop
Tyler Boone
2018-06-09 18:20:56
To better serve light clients and explorer
Fireduck
2018-06-09 18:21:32
ok
Tyler Boone
2018-06-09 18:21:38
makes sense
Tyler Boone
2018-06-09 18:22:05
just to confirm what that means. it's a new map in the DB class which will be saved onto disk using rocksDB
Tyler Boone
2018-06-09 18:22:26
so a new key-value lookup stored by the node
Tyler Boone
2018-06-09 18:24:15
Yes
Fireduck
2018-06-09 18:24:44
Using range queries in rocksdb for speed but you get the idea
Fireduck
2018-06-09 18:25:14
Since it is key to set rather than key to single value
Fireduck
2018-06-09 18:25:38
Old hat from my jelectrum days
Fireduck
2018-06-09 18:25:51
what kind of "set"?
Tyler Boone
2018-06-09 18:26:10
you have an example in here already?
Tyler Boone
2018-06-09 18:33:04
For an address the set of transactions involving it
Fireduck
2018-06-09 18:37:34
end of the day a ProtoDbMap stores a single message for a single value
Tyler Boone
2018-06-09 18:37:51
obviously a message can have a list in it. is that what you mean?
Tyler Boone
2018-06-09 18:37:56
Yes. Won't be using that.
Fireduck
2018-06-09 18:38:02
ok
Tyler Boone
2018-06-09 18:38:20
Don't want to rewrite entire set on new entry
Fireduck
2018-06-09 18:38:41
You can look in jelectrum code for set map examples
Fireduck
2018-06-09 18:38:54
I'll do something similar but better
Fireduck
2018-06-09 18:39:00
I know more now
Fireduck
2018-06-09 18:50:36
Basically key: address/txid value: null
Fireduck
2018-06-09 18:50:57
Query is get everything that starts with address/
Fireduck
2018-06-09 18:51:12
Rocks does that fast
Fireduck
2018-06-09 18:53:42
ah
Tyler Boone
2018-06-09 18:54:55
In Bitcoin some addresses have a million tx
Fireduck
2018-06-09 18:57:51
hmm, just started a new node with new db on my laptop and haven't had any indication of progress for 5 minutes...
Tyler Boone
2018-06-09 19:01:05
There is an open issue for that.
Fireduck
2018-06-09 19:01:21
No feedback while downloading headers
Fireduck
2018-06-09 19:02:30
in snowdb what is the 00003.log file?
Tyler Boone
2018-06-09 19:02:48
it's binary which is weird
Tyler Boone
2018-06-09 19:02:56
I would expect logs to be text
Tyler Boone
2018-06-09 19:03:42
It is rocks write ahead log
Fireduck
2018-06-09 19:03:48
Aka db journal
Fireduck
2018-06-09 19:04:27
ok
Tyler Boone
2018-06-09 19:12:48
@Clueless Can you give me a chunk of your pool logs? i want to know how fast and hard the shares are coming in to know how to prioritize issuing dynamic share difficulty to miners
Fireduck
2018-06-09 19:13:31
collusion!
Tyler Boone
2018-06-09 19:13:34
still kicking myself on not having file logging yet, but luckily the systemd setup I scripted for everyone logs to syslog by default. :D
Clueless
2018-06-09 19:18:30
hmmmm, I added a println statement into considerBlockHeader and I'm not seeing anything. let me see if I can get a stacktrace
Tyler Boone
2018-06-09 19:19:20
Might be not getting in touch with any peers
Fireduck
2018-06-09 19:20:06
WARNING: Please consider reporting this to the maintainers of com.google.protobuf.UnsafeUtil
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
Jun 09, 2018 12:16:38 PM snowblossom.node.BlockIngestor <init>
INFO: Loaded chain tip: 0 00000023440885bee85d7664235028ce89e21dae18edbdda2fe2ba35e3b664b7
Jun 09, 2018 12:16:38 PM snowblossom.node.Peerage <init>
INFO: Loaded 183 peers from database
Jun 09, 2018 12:16:38 PM snowblossom.node.Peerage start
INFO: Starting peerage
Tyler Boone
2018-06-09 19:20:11
looks likely
Tyler Boone
2018-06-09 19:21:12
Many of those peers don't actually accept connections
Fireduck
2018-06-09 19:21:20
a-holes
Tyler Boone
2018-06-09 19:21:26
It could take a while to find one that does
Fireduck
2018-06-09 19:21:35
Open an issue
Fireduck
2018-06-09 19:22:13
Maybe add a known good flag or use some of the peer info values for that
Fireduck
2018-06-09 19:24:08
probably connecting to lots of bad peers.
GitHub
2018-06-09 19:24:51
ok, lunch time
Tyler Boone
2018-06-09 19:43:49
[snowblossomcoin/snowblossom] Issue opened by fireduck64
GitHub
2018-06-09 19:44:17
[snowblossomcoin/snowblossom] Issue opened by fireduck64
GitHub
2018-06-09 22:04:48
*https://github.com/snowblossomcoin/snowblossom/compare/3aec9ddb84c8...3ceddc2c24c9*
https://github.com/snowblossomcoin/snowblossom/commit/3ceddc2c24c9de2ca67dcd8a97b8eac921da7675 - * Connect to peers faster
GitHub
2018-06-09 22:04:48
[snowblossomcoin/snowblossom] Issue closed by fireduck64
GitHub
2018-06-09 22:15:04
*https://github.com/snowblossomcoin/snowblossom/compare/3ceddc2c24c9...5eb7b7454e67*
https://github.com/snowblossomcoin/snowblossom/commit/5eb7b7454e67d5bcb9f42b0836a963f85f27b45d - Fix format bug
GitHub
2018-06-09 22:58:38
*https://github.com/snowblossomcoin/snowblossom/compare/5eb7b7454e67...611da775eb39*
https://github.com/snowblossomcoin/snowblossom/commit/611da775eb394f057a5e6e0007746143e0429242 - Working on mining pool dynamic difficulty
GitHub
2018-06-09 23:08:20
[snowblossomcoin/snowblossom] Issue closed by fireduck64
GitHub
2018-06-09 23:08:20
*https://github.com/snowblossomcoin/snowblossom/compare/611da775eb39...83f20a8e7fd4*
https://github.com/snowblossomcoin/snowblossom/commit/83f20a8e7fd4c5fb66c04f02c51719313e80cde4 - Dynamic pool diff
GitHub
2018-06-09 23:35:55
sigh... hacking on a someone else's already hacky codebase is hard
Tyler Boone
2018-06-09 23:38:24
Sorry, I did try to make it not a hack but had a tight timeline
Fireduck
2018-06-09 23:40:42
it's understandable
Tyler Boone
2018-06-09 23:40:51
actually I was just saved by one of our conversations
Tyler Boone
2018-06-09 23:41:03
I'm working on the hybrid mem-disk miner
Tyler Boone
2018-06-09 23:41:09
and I was getting shit hashrate
Tyler Boone
2018-06-09 23:42:16
and I remember you said you got shit hashrate because of sharing file handles across threads.
Tyler Boone
2018-06-09 23:44:14
Sweet, the hybrid miner should be fun
Fireduck
2018-06-09 23:45:04
looks like I it is starting to work...
Tyler Boone
2018-06-09 23:45:21
not as big an improvement as I was expecting. I might be doing something stupid...
Tyler Boone
2018-06-09 23:45:50
I mean... stupidity guaranteed
Tyler Boone
2018-06-09 23:47:34
INFO: Mining rate: 96518.365/sec - at this rate 1271.742 hours per block
Tyler Boone
2018-06-09 23:48:21
probably need to get a little more clever like we were talking about to take advantage of the memory more
Tyler Boone
2018-06-09 23:50:45
Probably a synchronize problem
Fireduck
2018-06-09 23:52:47
are you not operating a pool?
Tyler Boone
2018-06-09 23:55:05
Nope
Fireduck