fireduck 2017-01-18 08:55:39
APNG: should only need accuratish time if you are making blocks, otherwise it should be fine
APNG 2017-01-18 08:57:36
fireduck, do I need time for transactions?
maret 2017-01-18 09:05:16
Hi, whats the update around side chains? I've been hearing about them for about two years, there is always some update about some proposal but seems everything is too far from working in production
fireduck 2017-01-18 09:06:16
APNG: As far as I recall, transactions don't have times
fireduck 2017-01-18 09:06:35
They get included in a block which has a time but the transaction itself is timeless
fireduck 2017-01-18 09:06:41
like diamonds
APNG 2017-01-18 09:15:48
fireduck, what about delayed transactions or w/e?
fireduck 2017-01-18 09:16:20
APNG: I mean the data for a transaction literally does not contain a timestamp
fireduck 2017-01-18 09:16:35
so you can create a valid transaction having no idea what the time is
APNG 2017-01-18 09:16:56
ok
APNG 2017-01-18 09:18:20
fireduck, and how do you know how much you have available?
cluelessperson 2017-01-18 09:30:25
Question, how can you know if your private key goes to a compressed public key?
fireduck 2017-01-18 09:30:57
if it starts with L it is compressed
fireduck 2017-01-18 09:31:23
but there is a compressed and uncompressed public and private for every key
fireduck 2017-01-18 09:31:39
you can veiw with with bitaddress.org and 'wallet details' and paste in what you have
fireduck 2017-01-18 09:31:57
whoever invented compressed keys is literally satan
APNG 2017-01-18 09:32:56
how do you compress something that's supposedly random...
APNG 2017-01-18 09:33:06
oh wait, keys
APNG 2017-01-18 09:33:09
those aren't random
fireduck 2017-01-18 09:33:13
it saves you one byte maybe
APNG 2017-01-18 09:33:32
(well they are, just not like, they're not random numbers, since they need specific properties)
fireduck 2017-01-18 09:33:41
right
eennaam 2017-01-18 09:37:21
what is so evil about it
gmaxwell 2017-01-18 09:37:38
fireduck: what? it _halves_ the size of the public keys from 65 bytes to 33 bytes.
fireduck 2017-01-18 09:41:25
gmaxwell: can you show me an example? Maybe I've only seen the base58 representations that are very similar in size to uncompressed
fireduck 2017-01-18 09:41:47
eennaam: Added complixity for very little gain (but apparently I am wrong about that)
maret 2017-01-18 09:42:04
Hi, whats the update around side chains? I've been hearing about them for about two years, there is always some update about some proposal but seems everything is too far from working in production
gmaxwell 2017-01-18 09:43:31
fireduck: examples for G in hex, https://en.bitcoin.it/wiki/Secp256k1
