To date, every proposal to improve Bitcoin (BIP) that needed encryption alternatives to the invention of the wheel had to re -invent. Each one is combined with the implementation of his allocated Python for the Elliptic SECP256K1 and relevant algorithms, each of which is skillfully different from each other. These contradictions made quiet obligations and made BIPS review unnecessarily. This problem was recently highlighted in Newsletter Bitco Optting #348And this is at least a handful of developers in the Bitcoin Development Community for a long time: there should be a unified standard and reusable for the SECP256K1 reference symbol.
Last week, Jonas Nick and Tim Roving made Blockstream and Sebastian Falbesoner research. As part of the current Chilllydkg proposal, the team launched a version SECP256K1Lab. new , Uninterrupted Python Library for Initial Models, experimentation, and BIP specifications. It is not for use in production (because it is not a fixed time and therefore vulnerable to side canal attacks), but it fills a critical gap: it provides a clean and consistent reference for the SECP256K1 function, including the SCNORR Signature Signature Signatures, and the low-field/group ECDH/group. The goal is simple: make it easy and safe to write future BIPS by avoiding repeated applications for one time. For BIP authors, this means: less custom symbol, lower specifications problems, and a more clear path than the initial model to the suggestion.
> Why not only use the real SECP256K1 library?
Bitcoin Core already includes a fast and continuous CECP256K1. So why not only use the authors?
When the author of BIP offers a proposal, it is expected to include a reference to explain how the idea works. These applications should not be written in Python, but C is often low -level for initial models. Bethon is easier to read, easier to modify, and makes it more clearly what the author tries to express. These characteristics make them particularly suitable for writing specifications.
When introducing a new encryption idea, it helps to get something clear, brief and safe to experiment. In principle, such as tools such as HacSPEC It is a good option for formal specifications, because the HACSPEC is also a valid rust. But in practice, it may be difficult to work with HACSPEC, especially for BIP readers who are not aware of rust.
Python reads continues to make it the language that many authors return to when they need to explain how something works.
Why BIP authors continue to re -convert SECP256K1 over and over again
This started again with GDP 340When the author of BIP wrote the original reference code in Python, so it would be easy to follow mathematics. They have set exactly how to sign and check the SCNORR using SECP256K1 curved parameters. They had to build everything from zero point: the field account, collective operations, unlimited generation, and coding rules. Bethon’s symbol was clear and educational. But it is specifically designed on this only custom, and it has not been designed to be reused by that future.
Similarly, BIP 324 Transfer P2P encryptedAdd encryption to how to speak to Bitcoin contract with each other, and use a noise -based protocol dependent on the main exchanges, common secrets and similar encryption. While it depends on the same SECP256K1 curve used in BIP 340, it has not been re -used any actual implementation code. All encryption logic such as ECDH, sequence, and shaking hands from scratch in Bethon have been re -executed. Although basic mathematics is the same, all BIP ends with writing its own version of logic. This leads to a repeated effort and provides accurate contradictions.
What is SECP256K1Lab in reality
SECP256K1Lab It is the Python Library designed for one purpose: facilitating writing and testing the encryption specifications for Bitcoin. Python is already the most popular language and widely used for reference applications and tests in BIPS, so having a common and reusable library is logical. It is not designed to use production. It is designed for preliminary models, not performance. It provides a clean and uniform interface for the basic SECP256K1 function, with a readable and less prepared code. No more trader every time you want to test an idea or clarify how something should do.
Real world use: chilldkg
SECP256K1Lab It was first developed as part of work on ChilldkgNew BIP suggestion to generate distributed keys. Instead of writing another Python app for SECP256K1 only for this single specifications, the authors used the SECP256K1Lab to deal with all coding building blocks in a way that can be used by others. By reusing a common and readable code base, their hope is that BIPS encryption in the future will not have to start from scratch. With SECP256K1Lab, there is finally a basis for new proposals to depend on and improve together.
Where you can go
There is still an open question: Should SECP256K1Lab live in the BIPS warehouse? It already proves useful as a joint reference for encryption proposals, but there is a continuous debate about where he really belongs to the broader Bitcoin development process. Whether it is an independent library or become more tight with BIP workflow, there will be one clear thing – it fills a gap that has been around for years. If you are composed of BIP, specifications auditor, or curious about improving encryption tools around Bitcoin, we love your inputs. You can join the discussion on the Pretty Dave post menu or contribute directly to SECP256k1Lab GitHub Repo.
This is a guest function by Kiara Bickers. The opinions that are expressed are completely property and do not necessarily reflect the views of BTC Inc or Magazine Bitcoin.
The post An INSECURE Python Library That Makes Bitcoin Safer first appeared on Investorempires.com.
