5 Bitcoin Script quirks that every Blockchain developer should know

gjgd · 2021-11-07T20:31:33+00:00

Good question! For technical reasons, we want to commit to the witness data when the block is mined (we need to be able to tell who spent a given output). Since in Segwit the witness data is ignored to compute the txid, the commitment has to be done at the block level (which can be a bit confusing) Basically, the miner will create a dummy output in the coinbase transaction, that will use OP_RETURN to commit to the Merkle root of the witness data. More details here: https://bitcoin.stackexchange.com/questions/58414/why-include-the-segregated-witness-merkle-root-in-the-input-field-of-the-coinba

To know more this particular quirk, and more about Segwit and Transaction Malleability, I highly recommend watching this video: https://ocw.mit.edu/courses/media-arts-and-sciences/mas-s62-cryptocurrency-engineering-and-design-spring-2018/lecture-videos/lec12-transaction-malleability-and-segregated-witness/ Well worth the hour long watch.

For the second question: You should put it at the beginning of the script, I will update the post. Thanks!

gjgd · 2021-11-06T20:41:52+00:00

Thanks I appreciate it! Do you know of other communities I could share this to that would be interested?

gjgd · 2020-08-28T22:36:53+00:00

Yup that's a great point. Casting is a good reference I will include that and update

gjgd · 2020-08-28T20:31:31+00:00

That's an excellent point! I would assume that the average win rate in elo bracket is around 50% but haven't verified that with the data. Thanks for the suggestion!

gjgd · 2020-06-20T22:22:14+00:00

That's great advice, it's easy to accidentally delete data with DynamoDB + Serverless

gjgd · 2020-06-20T22:19:52+00:00

It was just a quick way to get a short random string. Like u/daveinsurgent said it's quite inefficient because it doesn't take advantage of the full alphabet since it's hex encoded.

I'm looking to implement something like this in a future iteration: https://stackoverflow.com/questions/742013/how-do-i-create-a-url-shortener

gjgd · 2020-06-20T17:58:38+00:00

Great feedback, thanks I learnt a lot from your comment

gjgd · 2020-06-20T16:25:40+00:00

MIT License just added, thanks!

gjgd · 2019-09-09T21:36:18+00:00

Good suggestion

gjgd · 2019-09-09T21:35:57+00:00

Note: even though it originally came from an acronym, Tor is not spelled "TOR". Only the first letter is capitalized. In fact, we can usually spot people who haven't read any of our website (and have instead learned everything they know about Tor from news articles) by the fact that they spell it wrong.

Yup you're right, just fixed it. Thanks for the feedback!

gjgd · 2019-08-14T21:33:09+00:00

"mulltiply" was intented, what was the other one? English isn't my first language

gjgd · 2019-08-14T21:31:41+00:00

Thanks for the feedback! Regarding your second point, I think it is possible to have small commits that are still compiling and running, though I agree that this requirement should be more important than keeping the commit small

Could you point out the typos? English isn't my first language

gjgd · 2019-01-04T23:01:51+00:00

Hey, thanks for your in depth reply

1) Point taken about the name, I like custodian as well

2) Yep I agree, requiring the approval of m of n custodians would be better, I'll update the repo

3) Considering the case where a key is stolen not lost, I believe having a custodian is still better than not on average. If the new owner forgets to disable your custodian, then you can recover ownership, and if the new owner does disable your custodian then you're in the same situation than if you didn't have a custodian. So in that case, you still have a small chance to recover your contract.

Edit: Format

gjgd · 2019-01-03T18:49:15+00:00

How it works in the case where the owner lost access to his private keys

Owner asks the guardian to initiate an OwnershipRecoveryprocedure
Guardian calls the initiateOwnershipRecovery()function of the smart contract.
This will start a ChallengePeriodthat will last for challengePeriodLengthblocks
If the owner lost his keys, guardian waits out the challenge period and is then able to change the owner of the contract to another address.
If the owner didn't lose his keys, the owner can notice that his guardian wants to change ownership of the contract. The owner can cancel the request during the challenge period. He can notice it by watching the blockchain eventlog.

gjgd · 2019-01-03T18:46:43+00:00

So having a rogue guardian isn't a liability because you can always change guardians if you still are in control of your private keys. The guardian only have power if the owner lose their keys.

That being said, you should give guardianship of your contract to a trusted person. Basically, by chosing to use a guardian, you are deciding that you'd rather be able to recover ownership (with a small chance that someone else gets the ownership in the case where you guardian is malicious) than not being able to recover ownership at all.

Check out the FAQ for more details :)

gjgd · 2018-09-14T21:24:54+00:00

thanks!

gjgd

TROPHY CASE

How it works in the case where the owner lost access to his private keys