archive snowblossom slack dev
prev 2018-06-10 next
2018-06-10 00:02:46
Tyler Boone
wait... does the pool miner not print out it's hashrate?
2018-06-10 00:03:22
Tyler Boone
ok, there it is
2018-06-10 00:05:19
Tyler Boone
ok, going to take a break for now
2018-06-10 00:05:56
Tyler Boone
if anyone wants to try the hybrid miner it's in tster/hybrid-miner for now
2018-06-10 00:06:34
Tyler Boone
INFO: Mining rate: 130666.289/sec that's with my 64gb memory desktop
2018-06-10 00:07:01
Tyler Boone
memfield_precache_gb=52
2018-06-10 00:22:54
Fireduck
From the pool side the hash rate is a wild estimate since it can only infer from shares
2018-06-10 00:23:14
Fireduck
And it is 20 second rate period
2018-06-10 00:23:21
Fireduck
So really nonsense
2018-06-10 00:23:32
Protovist
@Fireduck Pool diff increases if there are more than 3 shares per minute?
2018-06-10 00:23:52
Fireduck
Holy shit someone looked at my code
2018-06-10 00:23:55
Fireduck
Yeah
2018-06-10 00:53:33
Fireduck
@Protovist are you the silent pool operator?
2018-06-10 01:05:40
Protovist
Yes, I'm working on adding some UI.
2018-06-10 01:06:00
Tyler Boone
cool. what UI are you looking to do?
2018-06-10 01:06:05
Fireduck
Cool
2018-06-10 01:06:49
Fireduck
I was thinking of adding a get status Rpc to MrPlow so explorer can get info and show it
2018-06-10 01:08:19
Protovist
Just the basic miner/pool stats to start. Seeing if I can get rocksdb-node to read from plowdb.
2018-06-10 01:09:53
Fireduck
You are better off making a wrapping class that starts a node and MrPlow in the same process.
2018-06-10 01:10:20
Fireduck
Otherwise you'll have strange rocks read issues if something else it writting to it
2018-06-10 01:13:10
Protovist
Hmm, OK, I'll keep that in mind.
2018-06-10 01:15:25
Fireduck
If you want a review if whatever you are planning I'm happy to help but of course you can do whatever
2018-06-10 01:17:04
Protovist
Thanks. I'd like to just get something simple working ASAP, but we'll see how it goes...
2018-06-10 01:18:14
Protovist
How does the pool determine which address is used for the reward in the coinbase tx?
2018-06-10 01:18:43
Protovist
It doesn't seem to be the configured pool_address.
2018-06-10 01:19:28
Fireduck
Heh, that is the entirety of the magic
2018-06-10 01:19:55
Fireduck
It passes a weighted map of addresses and share counts to the node to build the coinbase
2018-06-10 01:20:04
Fireduck
Which directly pays the miners
2018-06-10 01:20:23
Fireduck
So easy, no pool wallet and payment processing
2018-06-10 01:21:38
Fireduck
The shares are managed by ShareManager
2018-06-10 01:24:12
Protovist
So is the address shown in the block explorer the highest weight?
2018-06-10 01:24:37
Fireduck
I think the explorer just shows the first one
2018-06-10 01:24:55
Fireduck
That isn't fancy
2018-06-10 01:25:04
Protovist
Having the payments in the coinbase directly is very slick..
2018-06-10 01:25:19
Protovist
The snowday pool always seems to have the same address shown.
2018-06-10 01:26:13
Fireduck
Probably same first address each time
2018-06-10 01:28:07
Fireduck
yeah, it is a treemap inside somewhere so ends up being alphabetic
2018-06-10 01:28:13
Fireduck
so it is that miner with the low address
2018-06-10 05:49:03
GitHub
[snowblossomcoin/snowblossom] Issue closed by fireduck64
2018-06-10 06:14:39
Fireduck
So...we have an issue
2018-06-10 06:15:05
Fireduck
I meant to make block reward half every 4 years. I apparently wrote 2 years in comments but actually implemented 1 year.
2018-06-10 06:15:21
Fireduck
https://github.com/snowblossomcoin/snowblossom/blob/master/lib/src/PowUtil.java#L178 ``` public static long getBlockReward(NetworkParams params, int block_height) ```
2018-06-10 06:15:36
Fireduck
So we could roll with it, or suggest a protocol change for sometime in the next year
2018-06-10 06:16:06
Clueless
If we make a protocol change, I highly suggest we do it sooner than later
2018-06-10 06:16:32
Protovist
If you're going to change it, a continuous reduction rather than a cliff would be nice.
2018-06-10 06:16:38
Clueless
Easier and more painless to do it now while everyone is more more capable of upgrading their systems and fewer people affected.
2018-06-10 06:18:35
Fireduck
@Protovist that is an interesting idea
2018-06-10 06:18:50
Clueless
@Protovist What doy ou mean cliff exactly?
2018-06-10 06:19:15
Clueless
there will be no cliff if we make the change quickly enough.
2018-06-10 06:19:55
Fireduck
I think he means rather than a big jump from 50 to 25 we do a slow scaling
2018-06-10 06:20:10
Fireduck
like one block is 49.5, the next is 49.48
2018-06-10 06:20:17
Protovist
Yes, precisely.
2018-06-10 06:20:26
Clueless
AH, yeah, I like that idea.
2018-06-10 06:20:30
Clueless
I prefer a formula.
2018-06-10 06:20:52
Clueless
Formula( Height ) => Current in Existence.
2018-06-10 06:51:05
Tyler Boone
if you public docs promise X and your code has a bug and delivers Y, I'm not sure I consider a vote appropriate for change. I would say it is proper to fix the code to match the original promise. Any nodes which haven't updated by the halving block will then end up forking. Likely no one currently in the community would still be running it, but if they are oh well, then there are 2 snowblossoms.
2018-06-10 06:51:46
Fireduck
I agree that makes sense
2018-06-10 06:52:03
Fireduck
but at this point, the safe and respectful thing to do is to make it a vote
2018-06-10 06:53:52
Tyler Boone
that's not hittable from here
2018-06-10 06:55:32
Fireduck
ipv6 only of course
2018-06-10 06:55:38
Fireduck
Transaction: afc78aa2b9feeb5c38d0b9107a5c61ae662749079e41249fa8f462c88532c163 size: 123 Coinbase - height:3617 remark:pool test 4 Motions Approved: 1 3 Motions Rejected: 2 4 Output: snowtest:emcpfwr7m5u6zmg3n4wmnz3lf4lz9h5ecarth54a 49.500000 Output: snowtest:yt60p2097jyf9prp2qd5v3p8cxl7673u2n7pwrfh 0.500000 Fee: 0.000000
2018-06-10 06:56:46
quantumblockz
Why are you only allowing ipv6
2018-06-10 06:57:01
Fireduck
just my internal network stuff on testnet
2018-06-10 06:57:23
Fireduck
I only have one ipv4 address, so most of my test and dev systems are ipv6 only from the outside
2018-06-10 06:58:07
quantumblockz
Is that just a obscurity measure to limit access?
2018-06-10 06:58:43
quantumblockz
Just curious because I haven't seen that before
2018-06-10 06:59:29
Fireduck
not at all
2018-06-10 06:59:53
Fireduck
on my home network, every VM I spin up has an ipv6 address that is reachable from the outside automatically
2018-06-10 06:59:58
Fireduck
so mostly I just use those
2018-06-10 07:00:40
Fireduck
so if I am testing something, it is likely to be ipv6 only
2018-06-10 07:00:52
Fireduck
and I tease anyone who can't access it
2018-06-10 07:01:04
quantumblockz
Lol I understand
2018-06-10 13:12:39
Rotonen
is there a pool operator quickstart somewhere or up to me to figure it out?
2018-06-10 13:13:40
Rotonen
@Tyler Boone when you do memory mapping of snow fields for the miner, if you can have the maximum per thread chunk match the maximum NUMA block on a symmetric multiprocessing system that'd help as well
2018-06-10 13:16:00
Rotonen
@Fireduck FYI shackleton still does not build for me on the 1.0.6 tag - seems like some build config issue as it's trying to write to a temp file which already exists
2018-06-10 13:17:18
Rotonen
``` ERROR: /Users/rotonen/koodaus/git/snowblossom/BUILD:38:1: Creating runfiles tree bazel-out/darwin-fastbuild/bin/Shackleton.runfiles failed (Exit 1) _bin/build-runfiles (args bazel-out/darwin-fastbuild/bin/Shackleton.runfiles_manifest bazel-out/darwin-fastbuild/bin/Shackleton.runfiles): mkdir '__main__/shackleton': File exists [17] ```
2018-06-10 13:17:51
Rotonen
for heterogenous systems it's a touch more complicated to figure out, but there's ample literature out there, snowblossom is sorta the same problem as any modern physics experiment is dealing with
2018-06-10 13:57:59
Rotonen
and figured this out from the source code as well
2018-06-10 14:04:34
Clueless
the Pool
2018-06-10 14:04:51
Rotonen
about, but i'm still not sure as to what the double for the pool fee means
2018-06-10 14:05:05
Rotonen
`1.0 == 100%` or `1.0 == 1%`
2018-06-10 14:06:42
Rotonen
pff reading comprehension, never mind
2018-06-10 14:08:11
Clueless
@Rotonen Reward * 0.01 => 1%
2018-06-10 14:08:19
Clueless
1.0 is 100%
2018-06-10 14:15:31
Rotonen
i suppose yours is the only currently public pool as it's in the docs and in the pool list
2018-06-10 14:23:09
Rotonen
namely now i also have one at `http://snowplough.kekku.li:23380` and unsure on what's appropriate for advertising
2018-06-10 14:40:22
Clueless
@Rotonen Feel free to mention it in general. I can put it : https://github.com/snowblossomcoin/snowblossom/wiki/9.-Mining-Pools if you want.
2018-06-10 14:40:52
Clueless
your HTTPS seems broken
2018-06-10 14:41:24
Rotonen
it does belong in the wiki, but yours will get most of the users as it's in the default config snippet section
2018-06-10 14:43:03
Rotonen
so rather have a pointer in that section to a pool list?
2018-06-10 14:43:13
Rotonen
ultimately there'd be a dynamic one with health statuses etc.
2018-06-10 14:47:20
Clueless
@Rotonen I believe in being fair and those are valid points. I will add health statuses and remove the default config
2018-06-10 14:48:37
Rotonen
rather than health, continent or so would probably be useful
2018-06-10 14:49:40
Clueless
@Rotonen continent? ...
2018-06-10 14:49:52
Clueless
man, I barely recognize the word.
2018-06-10 14:49:55
Clueless
agreed
2018-06-10 14:50:20
Rotonen
miners usually like to use a pool near them, for various reasons, which is not very important for snowblossom for now, but that'll cater to their expectations
2018-06-10 14:50:58
Clueless
@Rotonen How would you feel about me creating another url above yours for eastern hemisphere?
2018-06-10 14:51:19
Clueless
legitimately asking. I'm considering how I should enact policy on it for people putting pools up and wanting to group them together.
2018-06-10 14:51:51
Rotonen
indifferent, people who actually care just care of shortest-path ballpark
2018-06-10 14:52:06
Rotonen
so just group by country?
2018-06-10 14:52:23
Clueless
That works.
2018-06-10 14:52:33
Clueless
I would've figured they'd group by some other affiliation
2018-06-10 14:52:56
Rotonen
boils down to speed of light + crap at national borders
2018-06-10 14:54:31
Clueless
@Rotonen What are your pool fees? (including potential donation to fireduck)
2018-06-10 14:54:45
Rotonen
0.5%, 0 to the duck
2018-06-10 14:58:28
Clueless
playing dirty I see
2018-06-10 15:00:09
Clueless
@Rotonen Do you want any comment/remark on your info? ``` #SNOWPLOUGH #fee 0.5% pool_host=http://snowplough.kekku.li:23380 ```
2018-06-10 15:00:35
Rotonen
none, and dunno if the port needs to be there if it's the default one
2018-06-10 15:00:47
Clueless
that's default, I'll make it pretty
2018-06-10 15:02:56
Fireduck
I avoided putting any pool in the windows release config
2018-06-10 15:04:33
Clueless
Yeah, I only had it there because it was the only one in existence and a bunch of people wanted to jump in.
2018-06-10 15:06:04
Clueless
@Rotonen Sweet. https://github.com/snowblossomcoin/snowblossom/wiki/9.-Mining-Pools and I fixed it: https://github.com/snowblossomcoin/snowblossom/wiki/7.-Configs#poolminer Let me know if you have any other ideas/thoughts on fairness, even small ones, be petty.
2018-06-10 15:06:36
Clueless
That's not sarcasm, be petty. I prefer to identify things now rather than have people feel slighted later.
2018-06-10 15:07:55
GitHub
[snowblossomcoin/snowblossom] Issue opened by fireduck64
2018-06-10 15:08:48
Clueless
@Rotonen OH, better yet, I can set that entire codeblock to whatever you want in those 3 lines. :) Do you want to be named as pool operator?
2018-06-10 15:09:21
Rotonen
no, simple minimalism is my thing
2018-06-10 15:10:56
Clueless
secondly
2018-06-10 15:11:10
Clueless
As a matter of policy, should we require pool operators to be known/public? that's the sort of thing I prefer not to decide for everyone.
2018-06-10 15:11:35
Fireduck
Up to them I guess
2018-06-10 15:11:51
Clueless
Well, my concern is fraud.
2018-06-10 15:12:06
Clueless
If you're going to represent people, be known to them, sort of thing.
2018-06-10 15:13:07
Fireduck
I think people should be suspicious of unknown pool operators but I don't think we should have any policy about it
2018-06-10 15:14:38
Clueless
sounds fair.
2018-06-10 15:15:21
Shoots
agreed
2018-06-10 15:18:32
Rotonen
all my data is public via RIPE, for one
2018-06-10 15:18:40
Clueless
@Fireduck I like your comment on Pool failover. I was thinking about suggesting that myself given earlier discussion.
2018-06-10 15:21:15
Rotonen
if anyone actually wants to argue for non-anonymity as an inclusion criterion for pool operators, i'd like to see all listed pool operators chip in for a neutral 3rd party law firm arrangement to actually ID individuals across nationstates, but somehow that seems a bit heavyhanded
2018-06-10 15:28:23
Clueless
I was just slightly concerned about people complaining that we advertised someone that might scam them
2018-06-10 15:28:34
Clueless
(not you, but future postings)
2018-06-10 15:33:38
Fireduck
I guess if someone well know claimed to run a pool we should verify that it is them
2018-06-10 15:33:52
Fireduck
Known account on Reddit it Twitter or gpg
2018-06-10 15:34:01
Fireduck
But other than that..meh
2018-06-10 16:14:48
Clueless
@Rotonen Btw, my standard is, you can post it in the main channels on occasion, just don't spam. Discord, slack, etc. Maybe we should make an announcement channel.
2018-06-10 16:22:40
Protovist
@Clueless I think fraud is less of a concern with all the funds being paid out in the coinbase transaction.
2018-06-10 16:24:15
Clueless
I don't want to gatekeeper the community. just compartmentalizing my roles.
2018-06-10 16:25:37
Protovist
A dishonest pool operator could still alter the transactions, I suppose.
2018-06-10 16:26:58
Clueless
I mean down the line when snow is worth $1000 apiece.
2018-06-10 16:29:11
Clueless
`INFO: Error in send work: io.grpc.StatusRuntimeException: CANCELLED: call already cancelled`
2018-06-10 16:29:22
Clueless
pool thing, seems ominous
2018-06-10 16:30:18
Fireduck
Just a broken connection
2018-06-10 16:30:23
Fireduck
Not a problem
2018-06-10 16:32:43
Clueless
specifically, there's hundreds of entries/constant
2018-06-10 16:33:03
Clueless
just flooding logs, looks concerning
2018-06-10 16:54:10
Fireduck
Hum. Might need exception isolation for the notify loop
2018-06-10 16:54:22
Fireduck
Might be running out of connections
2018-06-10 16:54:35
Fireduck
But I am pretty busy today
2018-06-10 17:04:09
Fireduck
Any error from your miners?
2018-06-10 17:28:16
Clueless
I'm no longer mining personally, until I get more ram
2018-06-10 17:28:29
Clueless
hashrate seems lower than I'd expect.
2018-06-10 17:28:38
Clueless
but it's been fluctuating enough it's hard to tell
2018-06-10 17:28:57
Clueless
72,872,405 h/s is the average of the last 3 values in the last 5 minutes.
2018-06-10 17:31:21
Fireduck
Ok. Shouldn't get those errors more than occasionally
2018-06-10 17:31:45
Fireduck
I'll try to take a look
2018-06-10 17:34:37
Clueless
You take all the time you need
2018-06-10 17:44:31
Tyler Boone
someone else really needs to set up a pool
2018-06-10 17:44:37
Tyler Boone
I guess I can do it
2018-06-10 17:45:03
Fireduck
We have two
2018-06-10 17:45:09
Tyler Boone
oh sweet
2018-06-10 17:46:40
Clueless
There's 2 public, and I think 1 private
2018-06-10 17:46:45
Tyler Boone
nice, no fireduck donation on it
2018-06-10 17:46:46
Clueless
pending 1-2 more private
2018-06-10 17:46:50
Tyler Boone
screw that guy
2018-06-10 17:47:01
Clueless
lol, right?
2018-06-10 17:47:36
Fireduck
I like that there are secret private pools
2018-06-10 17:48:15
Clueless
there's a bit of concern about people objecting to raising the supply
2018-06-10 17:48:45
Clueless
I recommend early as possible to avoid polarization and potential splits
2018-06-10 17:49:19
Tyler Boone
you are asking early adopters to voluntarily dilute their blossoms by 4x
2018-06-10 17:49:28
Tyler Boone
of course, I think without doing it snowblossom is destined to fail
2018-06-10 17:49:45
Clueless
Exactly
2018-06-10 17:49:57
Clueless
I think the early adopters are smart enough to understand that.
2018-06-10 17:51:00
Clueless
also, would voting work based on current miners, or amounts of snow?
2018-06-10 17:51:08
Fireduck
Miners
2018-06-10 17:51:17
Clueless
hm.
2018-06-10 17:51:30
Clueless
Well miners may be inclined to allow the expansion so they can mine more
2018-06-10 17:59:06
Fireduck
We need someone to write up the proposal
2018-06-10 17:59:14
Fireduck
Give it a number
2018-06-10 18:00:33
Clueless
Write up proposal on wiki?
2018-06-10 18:00:44
Clueless
Can you also link me the line number for reference?
2018-06-10 18:02:40
Fireduck
Not at the moment, PowUtil getBlockReward or something
2018-06-10 18:02:55
Clueless
thanks will lookup
2018-06-10 18:03:18
Clueless
another perspective is that we could just add it in. As that's what's originally advertised. That's honestly a fix.
2018-06-10 18:05:26
Fireduck
Yeah, true
2018-06-10 18:05:34
Fireduck
But open is good, I think
2018-06-10 18:06:10
Tyler Boone
how long does the vote take?
2018-06-10 18:07:05
Tyler Boone
depending on the length, someone could spend a couple thousand to rent enough hashing power to win the vote
2018-06-10 18:08:15
Clueless
easily, that's my concern.
2018-06-10 18:08:52
Clueless
I think it's fair to stick to the intended design. Someone trying to exploit it should probably be ignored.
2018-06-10 18:08:56
Tyler Boone
doesn't sound like fireduck is as concerned about this problem as I am, which is fine
2018-06-10 18:08:56
Clueless
it's not like they were mislead
2018-06-10 18:09:05
Clueless
he's busy
2018-06-10 18:10:23
Tyler Boone
no, he doesn't consider the reduced halving time as big a deal as I do
2018-06-10 18:11:09
Tyler Boone
different priorities. it's fine
2018-06-10 18:37:20
Protovist
@Tyler Boone I'm planning to make my pool public as soon as I get some stats working.
2018-06-10 18:43:36
Protovist
@Fireduck The time it takes for difficulty to adjust is somewhat concerning. There's a very real potential for large mining pools to push up the difficulty and then abandon it once it's no longer profitable. This happened recently with VEO.
2018-06-10 18:44:39
Protovist
It's less of a concern since this isn't a GPU PoW, but still possible...
2018-06-10 18:44:44
Fireduck
It adjusts pretty fast. Hash power dropped hard yesterday and it is already steady
2018-06-10 18:45:59
Protovist
Oh. I guess I hadn't looked at the logs to check the rate.
2018-06-10 18:47:07
Protovist
Anyone here familiar with Angular?
2018-06-10 18:58:16
Clueless
What for? (but no)
2018-06-10 18:59:38
Protovist
Was trying to use it for the UI. :slightly_smiling_face:
2018-06-10 19:19:59
GitHub
Perhaps a configuration option to dictate the amount of recent history to cache.
2018-06-10 19:36:15
FxxNIHAO
@FxxNIHAO has joined the channel
2018-06-10 19:51:14
Fireduck
Jello
2018-06-10 19:51:49
FxxNIHAO
hi
2018-06-10 19:51:59
FxxNIHAO
how are you doing?
2018-06-10 19:54:00
Fireduck
Alright
2018-06-10 21:24:28
Fireduck
@Clueless I think those messages you were seeing about miners breaking connections is due to a bunch of miners connected by without the snowfield
2018-06-10 21:24:41
Fireduck
so they keep thinking they are stalled and restarting the connection
2018-06-10 22:03:11
Shoots
This is definitely a lot faster adjusting than veo. Is every 2000 blocks isn't it? It would be best to be instantly variable. Similar to what bismuth switched to.
2018-06-10 23:15:42
Fireduck
It actually shifts between blocks as well
2018-06-10 23:16:02
Fireduck
Diff drops slightly each new get block template