I'm thinking I'll build an order site on top of a snowblossom info side
maintain history, orders, autoclose after 24 hours
and provide an auth plugin in here/discord
@Clueless I wait
@gratisangratis what is that?
@Clueless The site
Ah. :)
How old are you ? @Clueless
28
(unfortunately)
why "unfortunately" ?
Bone spurs
while that is great, not what I meant to paste
I made some notes on new mining work
To whoever is mining a ton of blocks on a secret mining pool, can you vote yes on sip2?
I really love while my miner is starting up how Windows decides the 47gb I just loaded needs to all be paged out to disk
The new windows binary miner is hosted on http://debian.org
ok, anyone have any strong feels on encrypt entire wallet vs encrypt only the private keys?
fucking hell, as long as we are playing pki encryption, might as well use that to make is so client instances without the password can add new keys
ok, getting into keys about keys territory
thinking about having a single keypair that encrypts the wallet private keys
the problem there is on a password change, should really make a new keypair which means re-encrypting all keys
which is fine
but what we have a merge from an old version
ok, if we have a list of keypairs, we just add a new one on change password
old one stays around to handle any merges
not terrible but a little complicated
@Fireduck hahah, it's a rabbit hole.
some people will care about full wallet encryption, including metadata, others just care that it can't be spent.
@Fireduck enabling encryption should generate individual master keys for each wallet address as well as salt for any KDF Master keys should be encrypted using an intermediate key derived from a strong KDF of the user-entered password On password change, all master keys should be decrypted and re-encrypted using a new intermediate key. The master key itself (that encrypts the wallet private key) does not change This is mostly the model that Cryptomator and rclone uses Salts are encrypted as a part of this to prevent related key attacks, etc
should I work on the client or mining?
mining
client is fine for now
client is shit, but stable and working shit
yeah exactly nothing special but it works
I have issues with the miner, but no issues with the client
it needs a ton of work for exchange listing and business integration
miners make the network
plus I have an actual plan for the miner work
give us some love :kissing_heart::two_hearts:
sip2 has passed
so when we hit field 8 people using field 9 will have the advantage?
no
it's based on required minimum field, not actual field
hmm, I guess I dont quite understand SIP2
also I drank too much caffeine :grimacing::eyes:
do pool miners need to update for sip2 or just the nodes?
ideally everything
but just pools in smart
sometimes when I click the "B" for a block on the blockexplorer it doesn't load, just sits there loading and loading, but if I click it again it loads fine. Anyone else have this problem? Seems like a major priority issue, you're welcome for bringing it to your attention
Tyler did it
We have some sort of http bug
No rush on updating for SIP2 until we get close to field 8
I'd get more coding done if y'all got me a nanny
https://snowblossom.slack.com/archives/CAS0CNA3U/p1530212700000063 i’ll quote this until perpetuity Tyler did it
Which is funny because he had nothing to do with it and in fact tried to bring it to my attention
@Fireduck yeah, i’m a john cleese fan, so?
@Rotonen that quote isn't loading for me
We need to improve upon the user guide. Can anyone look at it and tell me what they think would go in it well?