scriptSig

Joined Sep 04, 2018

Profile not set

Mute
1PDBscfDpVrfZShDANtG9uaRumsBFnMDbK
Actions 423
Following 6
Followers 16
Topics following 5
Muted 6
Is Muted By 1

replied 2208d
1DYD9Y8EomqBapvM
It may not confirm. At the time of this writing, the fee is estimated to be 1.276 sat/B (per BU node). The size of your message was 377 B. 377*1.276=481 sat. Nothing to do with memo
replied 2208d
(cont) That way, the small fee pays for the service. But you're free to use whatever service you want to post memos if you don't like paying a few satoshi.
replied 2208d
Ugh, please, no. Not another ICO. A model to consider would be that each tx from the site sends micro payment to Memo.cash. Tx has 3 vout: change, OP_RETURN, Memo.cash fee. (cont)
voted Daily 2208d
created poll 2209d
I want to see how many people currently use Memo on a day to day basis. Stats page only shows total users. So with that in mind, how often do you visit Memo?
Weekly 2 votes · 0 satoshis
Daily 34 votes · 5,436 satoshis

Results

replied 2208d
Sk8eM dUb
Is this chess?
replied 2209d
My original thought was to use that, but it's bad crypto to use the signing key for encipherment (along with every other bad reason). Hope this helps!
replied 2209d
Here's a quick python script to convert that pub key to something you might recognize: https://imgur.com/a/kTr3qkS. So we publish our pub key to the block chain on every tx.
replied 2209d
Look at the scriptSig by clicking the Input Count, then view it by clicking "Sp Signature Hex": https://imgur.com/a/Q4RIYxl
replied 2209d
replied 2209d
When you expose the pub key, it's a privacy issue. But more importantly, if there's a weakness discovered where the priv key can be found with the pub key, your funds are protected.
replied 2209d
A few msgs coming. When you spend money, you have to publish the pub key in the scriptSig of the tx. That's why we have change addresses for EVERY tx: because you expose the pub key.
replied 2209d
Ahh I see that now, I apologize it's only my second day actually using memo. I just assumed you input the topic in your message. I didn't see create new on the topics page thanks !
replied 2209d
But my BCH pubkey for memo.cash is already public and available in these tx. Another rule of crypto: signing/with key is never used encipherment. Ever.
replied 2209d
It compromises your funds, your account, and every message you’ve ever sent. I was about to publish a spec on this and missed a crucial issue, so I’m re-thinking the design.
replied 2209d
Same reason why we don’t publish our public keys to the block chain, and when we do, we abandon them. It’s a complicated topic I can’t fit into 184 chars 😂
replied 2209d
And therein lies the problem. Crypto is more complicated than simply encrypting from a public key. I’ve been working on this for some time now.
replied 2209d
e34f3384e5affd6e04b595a5e640a0ded4d5158d37780aae25938c6af1f79d8e5f4f1c308778d7e3678c25ded2520de017106c372f1531c9a8d3c58482fc54dc8af6c2580e2e8aa327d89afc30b7957de7c2c620d309916715510c8f
replied 2209d
Are you trying to create one from memo.cash site? Topics -> New Topic. If you're trying to create the raw transaction: https://en.bitcoin.it/wiki/Script
replied 2209d
It has to be encapsulated into an output script.
2209d · test
🧀
replied 2209d
Yay python!
replied 2209d
Nikamoto
Aaaand there's the use case for a diff function so you can modify the text that's displayed for a post 😂
replied 2209d
bchdev
I sent in logs from the stress test. If the clients make changes and retest I hope they’re a little more specific in advance with what we should log and send in, like logging level
replied 2211d
I just won again!! But no TXID for the winnings 😫
replied 2211d
Ha. This is really going to confuse somebody in 30 years when they’re debugging, generate a random address, and can’t figure out why there’s $50 in it from an ancient block 😂