2018-06-26 04:56:08
I made stupid mistakes yesterday

Fireduck
2018-06-26 04:56:17
the address history work doesn't respect reorgs

Fireduck
2018-06-26 04:56:28
and could show things taht are not in the current main chain

Fireduck
2018-06-26 04:56:28
which is no good

Fireduck
2018-06-26 05:28:51
*https://github.com/snowblossomcoin/snowblossom/compare/e6870e182e8b...fb271f3d4b6e*
https://github.com/snowblossomcoin/snowblossom/commit/fb271f3d4b6e5f2a9eac6c4e134a30c3847b6d79 - Address history now properly reports with reorgs

GitHub
2018-06-26 05:29:33
Anyone running my address history code from last night should do a db nuke and recreate

Fireduck
2018-06-26 05:29:42
with addr_index

Fireduck
2018-06-26 05:29:51
if not using addr_index, there is no difference

Fireduck
2018-06-26 05:31:52
@Fireduck good thing I missed you have to do addr_index

Clueless
2018-06-26 05:37:16
hah

Fireduck
2018-06-26 05:37:25
you don't need it unless you have an explorer attached

Fireduck
2018-06-26 18:45:50
Have you guys started working on a BTC style RPC for exchanges to use?

Shoots
2018-06-26 19:04:10
do exchanges sponsor that sort of work?

Rotonen
2018-06-26 19:25:27
@Shoots not yet. My hope is to get in touch with an exchange and get a rough set of requirements to work towards

Fireduck
2018-06-26 19:25:32
rather than guessing what they want

Fireduck
2018-06-26 19:26:42
I'm pretty sure all exchanges look for an RPC that mirrors BTC

Shoots
2018-06-26 19:27:24
sure, but there are a bunch of questions. Do they want one wallet per customer? Do they want notifications or are they happy to poll when a user logs in?

Fireduck
2018-06-26 19:34:13
@Fireduck if you wanna raise eyebrows and make a splash, don’t do cointopia as the first one

Rotonen
2018-06-26 19:35:10
I am aware of that terrible json rpc protocol

Fireduck
2018-06-26 19:35:49
terrible maybe, but thats how most if not all exchanges handle RPC

Shoots
2018-06-26 19:36:06
sure, and it has about 100 calls. It would be good to know which ones anyone cares about.

Fireduck
2018-06-26 19:36:47
@Rotonen why is cointopia some sort of list anything that moves exchange?

Fireduck
2018-06-26 19:38:29
These guys seem like they're pretty decent for getting back to dev's https://crex24.com/

Shoots
2018-06-26 19:40:22
Are they going to be irritated when I answer "What listing fee do you propose to pay?" with "Nothing" ?

Fireduck
2018-06-26 19:40:36
Or is that a gate question to eliminate terrible scams

Fireduck
2018-06-26 19:40:38
heh

Fireduck
2018-06-26 19:40:42
doesn't really matter

Fireduck
2018-06-26 19:41:43
not sure why they would be irritated.

Tyler Boone
2018-06-26 19:41:56
respond with "We are an honest hard working community that believes projects started with no premine deserve a free listing."

Shoots
2018-06-26 19:43:09
DEFT just got listed on that exchange and it actually seems decent. The guy they were dealing with seemed to be responding very fast and they actually set a trading launch date that they hit.

Shoots
2018-06-26 19:44:25
nice

Fireduck
2018-06-26 19:45:18
alright, I'm all over it

Fireduck
2018-06-26 21:56:51
@Fireduck 'not even on cointopia yet' is a sign of freshness of new currencies

Rotonen
2018-06-26 22:19:04
@Fireduck `INFO: Mining rate: 0.000/sec - at this rate ∞ hours per block` is common when not having many miners, how does it decide that? also claims being stalled

Rotonen
2018-06-26 22:19:28
I should fix that

Fireduck
2018-06-26 22:19:44
```
INFO: Mining rate: 5-min: 1.007M/s, 15-min: 997.312K/s, hour: 808.569K/s
Jun 26, 2018 10:18:53 PM snowblossom.miner.MrPlow printStats
INFO: Mining rate: 0.000/sec - at this rate ∞ hours per block
Jun 26, 2018 10:18:53 PM snowblossom.miner.MrPlow printStats
INFO: we seem to be stalled, reconnecting to node
```

Rotonen
2018-06-26 22:19:48
It is assuming no shares in 20 seconds is a problem

Fireduck
2018-06-26 22:20:33
well, especially with the difficulty ramp up creep issues, that'll jam things up a bit

Rotonen
2018-06-26 22:20:38
what's the cost of it hitting that, actually?

Rotonen
2018-06-26 22:27:54
None

Fireduck
2018-06-26 22:28:33
good, just from time to time wondering if there is actually something wrong with the pool as relatively many people try it a bit and leave

Rotonen
2018-06-26 22:29:07
grepping the logs i've had 100+ addresses on within 24h, but like 99% of the shares are mine

Rotonen
2018-06-26 22:29:36
i'll go with 'most people are confused'

Rotonen
2018-06-26 22:32:11
what pool do you run?

Tyler Boone
2018-06-26 22:33:01
snowplough?

Tyler Boone
2018-06-26 22:33:21
yeah, snowplough is mine

Rotonen
2018-06-26 22:33:32
I mine on that pool

Tyler Boone
2018-06-26 22:33:52
but it's my gaming machine, so I kill the miner often

Tyler Boone
2018-06-26 22:34:06
by "my gaming machine" I mean "my only computer"

Tyler Boone
2018-06-26 22:34:38
i guess you're the frequent 100k range miner then

Rotonen
2018-06-26 22:35:07
yup

Tyler Boone
2018-06-26 22:35:40
you do about the same as i do, throw spare capacity at it

Rotonen
2018-06-26 22:36:07
though mine bursts to some 30M range if everything is idle (but this essentially never happens, though, as my infra is mostly actually doing stuff)

Rotonen
2018-06-26 22:37:27
the one i have constantly there just to show there is any mining going on, is actually testing over different combinations of jvm and miner parametres slowly

Rotonen
2018-06-26 22:37:44
haha, nice

Tyler Boone
2018-06-26 22:38:29
so far nothing is out of the ordinary very much

Rotonen
2018-06-26 22:39:18
but i actually reach the same terminal mining speed without memfield as with memfield, it just takes like 2 days

Rotonen
2018-06-26 22:40:15
so memfield and hybrid are actually only mitigate a slow warmup

Rotonen
2018-06-26 22:41:27
the max depth parameter will make a difference

Tyler Boone
2018-06-26 22:41:46
if you can't fit the entire field into memory

Tyler Boone
2018-06-26 22:43:01
what's that actually controlling and is that on a branch?

Rotonen
2018-06-26 22:43:28
that causes the miner to drop a piece of work on the floor if it has to go to disk early in the hash chain

Tyler Boone
2018-06-26 22:43:37
each POW has 6 hashes (as you know)

Tyler Boone
2018-06-26 22:44:13
so if you set it to 2, then if the first or second hash can't be served from memory, it will drop it on the floor

Tyler Boone
2018-06-26 22:44:42
i think i'd rather let it pull new stuff into the cache - that'll average out over time

Rotonen
2018-06-26 22:45:03
but i suppose if you precache as in hybrid, that'd then pull more hashes, but decrease the collision chance?

Rotonen
2018-06-26 22:45:05
this is for miners who can't cache the entire snowfield

Tyler Boone
2018-06-26 22:45:09
is that actually a good thing?

Rotonen
2018-06-26 22:45:34
yeah, but that'll kink the search distribution, right?

Rotonen
2018-06-26 22:45:46
yeah, but who cares?

Tyler Boone
2018-06-26 22:46:11
i'm not convinced that's actually conductive to block hit rates

Rotonen
2018-06-26 22:46:43
when I had 51gb of 64gb in memory it bumped my hashrate from ~110k to ~230k

Tyler Boone
2018-06-26 22:47:02
gotta run

Tyler Boone
2018-06-26 22:47:03
ttyl

Tyler Boone
2018-06-26 22:47:04
sure, but quality of collision attempts makes that apples to oranges

Rotonen
2018-06-26 22:47:24
nah, it's just trading extra CPU for less disk io

Tyler Boone
2018-06-26 22:47:24
or rather you're trading entropy quality off for density

Rotonen
2018-06-26 22:47:33
rather do zram or something for that

Rotonen
2018-06-26 22:47:49
the miner itself gets bumped into zram first

Rotonen
2018-06-26 22:48:00
and that compresses well, also thread overlaps do

Rotonen
2018-06-26 22:49:39
if you do that across many miners, and you can have offsets for the precache range, and you have enough miners to cover the whole field, that will work

Rotonen
2018-06-26 22:49:59
but that'd require the pools to orchestrate that and the miners to ask for allocation ranges from the pools

Rotonen
2018-06-26 22:50:13
so summa summarum i do see a use for the feature

Rotonen
2018-06-26 22:50:58
that'd actually allow everyone to do ram-only or hybrid, but share value counts get a lot more complicated

Rotonen
2018-06-26 23:04:33
the case can be made pretty easily using an argument ad absurdum

Tyler Boone
2018-06-26 23:05:40
imaging you have 1GB of storage with almost unlimited throughput (like 1pb/sec), and all other storage is extremely low throughput (like 10 bytes/sec).

Tyler Boone
2018-06-26 23:05:50
and you have 10,000 cores

Tyler Boone
2018-06-26 23:06:33
it will be more effective to use all those cores to search for a POW which does all 6 hashes within the 1GB of ulta-fast storage

Tyler Boone
2018-06-26 23:06:47
that it would be to use the 10 byte/sec throughput

Tyler Boone
2018-06-26 23:07:04
Miners are already segregated with separate nonce prefixes

Fireduck
2018-06-26 23:07:43
WTB one tboone machine

Fireduck
2018-06-26 23:13:18
BTW, @Rotonen, the feature is in master, but I don't know if it is in a release. you can test it out by using min_depth_to_disk=<x> in your miner's config file.

Tyler Boone
2018-06-26 23:13:37
it's only applicable if using memfield_precache_gb for some amount smaller than the entire snowfield

Tyler Boone