Even the wheel continues to evolve in practice.
Almost all base code of all OS's etc will be rewritten by IA and will be more efficient.
For now I'm just concentrated in libraries that don't belong to JS engine and have much more code than what I need.
Maybe in future I'll make a movie step by step how to generate a taproot address only with pen and paper for Guiness records !
To understand all the process I need to isolate the less code possible to start studying it.
All the code have bugs or can be improved, If there is nobody reading, it can't evolve.
For some reason we are using Taproot now and we don't became forever on Legacy.
There is not only one library for same features, the idea is to select the best approach of each one.
When I started learning to code I was taught that the most important was algorithm.
That was a universal language that could be converted in any code language.
Any big work need to have a project, so, one algorithm is the best project for bitcoin, where is that algorithm for next generations could learn about bitcoin and maybe improve it?
With this type of approach I think we should change the slogan to: "Don't verify, just trust!"
Topic: Javascript Taproot Address Generator for Browser - page 2. (Read 300 times)
Hi,
I'd like to know if there is ppl that would like to help to develop a Javascript Taproot Address Generator for Browser.
I have been working on that since some time and the idea is to make the simplest address generator possible in a standalone file, without using complicated libraries full of code that makes any guy just want to trust and not verify.
I'd like to know if there is ppl that would like to help to develop a Javascript Taproot Address Generator for Browser.
I have been working on that since some time and the idea is to make the simplest address generator possible in a standalone file, without using complicated libraries full of code that makes any guy just want to trust and not verify.
The lines of code contained in popular libraries are complex and very extensive. But there is a reason for that.
They aren't complex to make you confused when verifying. They are complex because they are tested, secure, efficient and accurate.
You shouldn't spend your time reinventing the wheel. This is not how new techs evolve.
By doing what those professional libraries do in your own way, you will probably create an insecure and inefficient software.
For learning purposes you are making a nice initiative. But only for that.
I'm trying to made bitcoin not only for nerds.
One example of a bitcoin JS library terms and conditions of use, that is already used by many that don't understand it:
One example of a bitcoin JS library terms and conditions of use, that is already used by many that don't understand it:
Sorry to say, but that's a stupid argument. Find me a single piece of open source software or license that doesn't include a "NO WARRANTY" clause. Even if you choose not to use the open source BitcoinJS-lib, you'll still be using a web browser and its underlying JS engine. Have you bothered checking what their licenses say?
I'm trying to make bitcoin not only for nerds.
One example of a bitcoin JS library terms and conditions of use, that is already used by many that don't understand it:
"Be aware: this library is Apache licensed. By using it, you agree with the terms of that license.
In particular pay attention to section 7 and 8, which assert there is NO WARRANTY that this library is safe to use or bug free, and in fact that by using this code you accept that none of the contributors shall be liable for any damages or monetary loss that results from your use of their code, even if due to bugs in that code. In short, according to the license the library is distributed under, there are no situations in which you could sue any of the developers (it's as if you wrote the entire library yourself). If you can't handle that, don't use this library."
The bitcoin slogan is: "Don't trust, verify!"
First step is to make a step by step manual as easier as possible, with only the code to generate addresses and forget everything else.
Generating secure addresses is the heart/core of bitcoin and nobody is doing it, a beginner can forget everything else as how to mine, how to run a node, can't forget how to generate safe addresses and many, many are mining and running nodes that don't know how to generate safe addresses, even the code of bitcoin core is questionable about the security of generating addresses safely.
The news about robberies come to the internet every single day, so, we need to have simple manual step by step for the ones that would like to learn.
I'm here ready to learn and teach what I already know, if somebody could help many will appreciate.
One example of a bitcoin JS library terms and conditions of use, that is already used by many that don't understand it:
"Be aware: this library is Apache licensed. By using it, you agree with the terms of that license.
In particular pay attention to section 7 and 8, which assert there is NO WARRANTY that this library is safe to use or bug free, and in fact that by using this code you accept that none of the contributors shall be liable for any damages or monetary loss that results from your use of their code, even if due to bugs in that code. In short, according to the license the library is distributed under, there are no situations in which you could sue any of the developers (it's as if you wrote the entire library yourself). If you can't handle that, don't use this library."
The bitcoin slogan is: "Don't trust, verify!"
First step is to make a step by step manual as easier as possible, with only the code to generate addresses and forget everything else.
Generating secure addresses is the heart/core of bitcoin and nobody is doing it, a beginner can forget everything else as how to mine, how to run a node, can't forget how to generate safe addresses and many, many are mining and running nodes that don't know how to generate safe addresses, even the code of bitcoin core is questionable about the security of generating addresses safely.
The news about robberies come to the internet every single day, so, we need to have simple manual step by step for the ones that would like to learn.
I'm here ready to learn and teach what I already know, if somebody could help many will appreciate.
Taproot support was added in the v6.1.0-rc.0 version of BitcoinJS-lib, so I don't see what your problem is. To clarify, I'm not advocating for bloatware or using libraries for tasks that can be done manually. However, considering the complexity of the problem you're trying to solve and the potential pitfalls, especially if you're not an experienced coder, this is a perfect example of where using a professionally made and thoroughly tested library makes sense and is justified.
I will lunch first doubt to see if someone could help.
From this x-only form coordinate point:
X= 60376045308133502588319041039213905409191423390227563583774073057371619898448 (decimal)
X= 857BA1721C71D8F80F9C208B513BEEAC46816A4123FB7DB11A3CF6833D58B450 (hexadecimal)
What is the next step to get this final taproot address:
BC1PY5VKU7TV8A39WPE6LQF3P6W5JMC3CMHTWCQ3WHYTW59MCH7542JSFYEMK9
?
From this x-only form coordinate point:
X= 60376045308133502588319041039213905409191423390227563583774073057371619898448 (decimal)
X= 857BA1721C71D8F80F9C208B513BEEAC46816A4123FB7DB11A3CF6833D58B450 (hexadecimal)
What is the next step to get this final taproot address:
BC1PY5VKU7TV8A39WPE6LQF3P6W5JMC3CMHTWCQ3WHYTW59MCH7542JSFYEMK9
?
Hi,
I'd like to know if there is ppl that would like to help to develop a Javascript Taproot Address Generator for Browser.
I have been working on that since some time and the idea is to make the simplest address generator possible in a standalone file, without using complicated libraries full of code that makes any guy just want to trust and not verify.
I'm trying to find ppl that have full knowledge of the process since the X-only coordinate until the final bech32m encoding to generate the BC1P... address.
As I said the idea is not just use some public libraries and make it work, that I already have, the idea is to isolate all the code and explain it step by step for any newbie that understands or pretend to learn coding could understand fully what is being done.
Someone would like to help?
I'd like to know if there is ppl that would like to help to develop a Javascript Taproot Address Generator for Browser.
I have been working on that since some time and the idea is to make the simplest address generator possible in a standalone file, without using complicated libraries full of code that makes any guy just want to trust and not verify.
I'm trying to find ppl that have full knowledge of the process since the X-only coordinate until the final bech32m encoding to generate the BC1P... address.
As I said the idea is not just use some public libraries and make it work, that I already have, the idea is to isolate all the code and explain it step by step for any newbie that understands or pretend to learn coding could understand fully what is being done.
Someone would like to help?
Jump to: