 Show Posts
|
|
Pages: [1] 2 »
|
Recently, the people applying for s BTC are all newbie. I need a way to verify that they are not the same person. I've never used Signet, but isn't the point of Signet that you have millions of coins at your disposal? Other than testing, I don't get why anyone would try to get many coins. Couldn't they create their own Signet if they wanted that? 1. Bitcoin ecological projects are developing rapidly, and many projects require test coins for community testing. This may bring potential demand and trigger some people to maliciously hoard test coins and sell them for profit in the future. 2. If you are an independent developer, deploying a local regression test network is a better choice than deploying a signet network; however, if you are driving a community to test the Bitcoin project, a public test is needed at this time network, such as testnet3/4 or signet.
Can u send me some sBTC? i wanna try signet too. Thx
tb1p8wk5jxzuydnkpyur4f0dsczxp6zytpnv4pa2wq0c72f6nujdlyvsaetj9c
please contact me via telegram invite link: https://t.me/+QO2WDLnHkBgyZDI1[moderator's note: consecutive posts merged] |
|
|
|
please contact me via telegram invite link: Why's that? What happened to just using addresses? Recently, the people applying for s BTC are all newbie. I need a way to verify that they are not the same person. Thanks for @BabyBandit's reminder. So I gave the telegram link way. |
|
|
|
Your help is awesome. I'm a new user and really want to try this but the sbtc faucet seems impossible, I hope you can gift me some sbtc. I really appreciate your help. My wallet: tb1pm7uz4yhnsha5rvdfzkfvx7ds8fu9ent6s4z8zw85xcwc9lfs8vgqk984mu
please contact me via telegram invite link: https://t.me/+QO2WDLnHkBgyZDI1 |
|
|
|
hi ethan, thanks for your great job. will you please send me a little sBTC? I want to try.
MY SIGNET ADDRESS:tb1pz4483tyhz9yqhzq5fzfj6c83c8460hdcrx3r9jav9mf9vrkcr50sn98mwh
Thank you
1 sBTC has been sent. txid: https://signet.sathub.io/tx/f5f1421d993a458fb5e77863a9fe11deafaa44fe19a43322fc2cc070a7945676
Obviously, the testnet's block production is unstable, and the old signet is not easy to get sBTC. In order to facilitate developers, I recently launched a new signet network, including: 1. Three block-mining nodes; 2. A browser based on mempool open source software; website is: https://signet.sathub.io3. An electrumx service; 4. An rpc and synchronization node; 5. signet faucet(will be open in the future); How they are connected can be seen in the documentation， https://docs.sathub.io/sathub-docs/connectThe main portal for the service is： https://sathub.ioEveryone is welcome to use it, it is free; it is currently in the trial operation stage, if you want to participate, please contact me via message box or reply this topic directly and I will give you some sBTC; I will continue to invest time and effort in this matter to provide the community more options choice； Hello Mr Liu! You can to send me some sBTC to the address: tb1qmtwh4wg0y9zxeejfslu6krg9gezvsuvsrs4zhq Thanks You So Much.  done. https://signet.sathub.io/tx/c9ea93b47aad1f0b9ae09c3084354b1638f8ef5577fd09e1a79fb4c7344c677acan you send me some btc signet ? thank you, my address: tb1pazgupd2ws7fuqeugev4l3tgk0vq2ltazzra76eraj2v0909s6twq76xx8y 0.1 sBTC has been sent. txid: https://signet.sathub.io/tx/b352d7fbdc25b322a8778e638dbaa62da21b6a95e1b62cdf53fd1cce6e3c7e05if you want more, please feel free to contact me directly. [moderator's note: consecutive posts merged] |
|
|
|
Obviously, the testnet's block production is unstable, and the old signet is not easy to get sBTC. In order to facilitate developers, I recently launched a new signet network, including: 1. Three block-mining nodes; 2. A browser based on mempool open source software; website is: https://signet.sathub.io3. An electrumx service; 4. An rpc and synchronization node; 5. signet faucet(will be open in the future); How they are connected can be seen in the documentation， https://docs.sathub.io/sathub-docs/connectThe main portal for the service is： https://sathub.ioEveryone is welcome to use it, it is free; it is currently in the trial operation stage, if you want to participate, please contact me via message box or reply this topic directly and I will give you some sBTC; I will continue to invest time and effort in this matter to provide the community more options choice； Hello Mr Liu! You can to send me some sBTC to the address: tb1qmtwh4wg0y9zxeejfslu6krg9gezvsuvsrs4zhq Thanks You So Much. done. https://signet.sathub.io/tx/c9ea93b47aad1f0b9ae09c3084354b1638f8ef5577fd09e1a79fb4c7344c677a |
|
|
|
Hi! send me pleace some sBTC for test:
tb1q6wyx49m96pry5nxg9lfqlrce940fldnnwz6ew
thanks!
Hi Sir, your received address of signet is incorrect, please check it again. |
|
|
|
Your reply reminds me that I should further improve the miner program to make the entire signet network more stable; Yes, this attack can be easily avoided, if all other nonces will lead to weaker blocks. So: if you for example always scan all 2^32 nonces, and make sure, that there is only one nonce, giving a valid block hash, then nobody can change it. And if you don't want to burn more power, then another possible change, is to always require a particular nonce, in case of a conflict. For example: you can require putting the lowest possible nonce, if there are two competing ones. Then, even if someone will submit another nonce, it can be easily rejected, by a simple condition, like " if(nonce2>nonce1) rejectBlock();". good suggestion. |
|
|
|
|
Your work is very meaningful. I will help you promote this book and introduce it to my friends around me; when you put this book on Amazon, I will buy it as soon as possible.
give you my respect again.
|
|
|
|
Sometimes, mining machines come in for testing, and block reorganization and transaction loss may occur. Anyone can try to create a single block reorganization in signet, here is how: 1. You fetch the latest signet block, for example: $ ./bitcoin-cli -signet getblock 00000336aaef9a23c8c26aaed301ee8dbd56706c1f5abd38231b920c62a59f7a 0
000000200650e5ac197ded8626635ff33cd8a6de40e3a8a6ec6abecd5ebf34fee9010000a543fb6e381fc83674162e761c2b4204c2aec50ba3c8bb96415295228255b8c626a5c566ae77031e4bb2770001020000000001010000000000000000000000000000000000000000000000000000000000000000ffffffff03024904feffffff0200f2052a010000001976a914a92e25d7da68b0f86d53780c52f6a3007a95877e88ac0000000000000000776a24aa21a9ede2f61c3f71d1defd3fa999dfa36953755c690689799962b48bebd836974e8cf94c4fecc7daa2490047304402205d839e3682fcf85fa6d3d8500e77f9d3027f78af21016de96a2a3bd8b1352d6d02206b891de7d77e7305468d4a0e26adb58d8cda6a22a22a10ab5f8c32047162df8901000120000000000000000000000000000000000000000000000000000000000000000000000000 2. You grind another header, with a different nonce: $ ./bitcoin-cli -signet getblockheader 00000336aaef9a23c8c26aaed301ee8dbd56706c1f5abd38231b920c62a59f7a false
000000200650e5ac197ded8626635ff33cd8a6de40e3a8a6ec6abecd5ebf34fee9010000a543fb6e381fc83674162e761c2b4204c2aec50ba3c8bb96415295228255b8c626a5c566ae77031e4bb27700
$ ./bitcoin-util grind 000000200650e5ac197ded8626635ff33cd8a6de40e3a8a6ec6abecd5ebf34fee9010000a543fb6e381fc83674162e761c2b4204c2aec50ba3c8bb96415295228255b8c626a5c566ae77031e00000000
000000200650e5ac197ded8626635ff33cd8a6de40e3a8a6ec6abecd5ebf34fee9010000a543fb6e381fc83674162e761c2b4204c2aec50ba3c8bb96415295228255b8c626a5c566ae77031e008c6c04 3. You submit a slightly modified block to the network: $ ./bitcoin-cli -signet submitblock 000000200650e5ac197ded8626635ff33cd8a6de40e3a8a6ec6abecd5ebf34fee9010000a543fb6e381fc83674162e761c2b4204c2aec50ba3c8bb96415295228255b8c626a5c566ae77031e008c6c0401020000000001010000000000000000000000000000000000000000000000000000000000000000ffffffff03024904feffffff0200f2052a010000001976a914a92e25d7da68b0f86d53780c52f6a3007a95877e88ac0000000000000000776a24aa21a9ede2f61c3f71d1defd3fa999dfa36953755c690689799962b48bebd836974e8cf94c4fecc7daa2490047304402205d839e3682fcf85fa6d3d8500e77f9d3027f78af21016de96a2a3bd8b1352d6d02206b891de7d77e7305468d4a0e26adb58d8cda6a22a22a10ab5f8c32047162df8901000120000000000000000000000000000000000000000000000000000000000000000000000000 4. You can then see a different block hash in chain tips: $ ./bitcoin-cli -signet getchaintips
[
{
"height": 1103,
"hash": "0000002efba5692bb5069e04619486257292b1f0c963c67f73a2828fa3f2a8bc",
"branchlen": 0,
"status": "active"
},
{
"height": 1097,
"hash": "00000048c88ac6e72c6b27b21498e5fb5a36a1e60dbcb47ac659af2e6cc03dfb",
"branchlen": 1,
"status": "valid-headers"
}
] And then, if some of your peers is on a block 1097, then that peer doesn't know, if the valid block is 00000048c88ac6e72c6b27b21498e5fb5a36a1e60dbcb47ac659af2e6cc03dfb or maybe 00000336aaef9a23c8c26aaed301ee8dbd56706c1f5abd38231b920c62a59f7a. Eventually, it will be solved, but you have to wait for the next block, to know that. This trick works mainly because nonces from block headers are not signed. Edit: Also note, that if you have very low minimal difficulty, then there is a huge potential for nonce grinding. Let's calculate it: 1d00ffff->00000000ffff0000000000000000000000000000000000000000000000000000
1e0377ae->00000377ae000000000000000000000000000000000000000000000000000000
ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff/00000000ffffffffffffffffffffffffffffffffffffffffffffffffffffffff=100000000
ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff/00000000ffff0000000000000000000000000000000000000000000000000000=100010001
ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff/00000377ae000000000000000000000000000000000000000000000000000000=49d414
100000000/49d414=377
0x377=887 Which means, that in case of your difficulty, for each and every block, it is possible to create something around 887 alternative block hashes, on average. Which also means, that if the validity of the block is not pre-defined somehow, then malicious actors can spread some block headers to different miners, and they will waste a lot of hashrate, before coming into consensus. As I can see, your signet challenge is 1-of-3 multisig. So, I guess, it is planned to have at least three different nodes, acting as miners. So, it is possible to observe new block headers, and for each and every header, a malicious node can broadcast around 887 different hashes, with different nonces. Then, two other mining nodes may receive those alternative headers, in a different order, depending on how nodes are connected. So, as you can see, reaching reorg-resistance is not that obvious, as it seems to be. But of course, if there is only a single miner at a given time, then it can trust its own blocks, and reject everything else. Thank you for your detailed and wonderful reply, it’s great; If the signet we build is a completely open network, and each miner node is completely independent, the situations you mentioned will occur, grinding a new block multiple times in a block generation cycle will lead to block reorganization, which will bring great challenges to the stability of the network. On the other hand, according to my understanding, signet is a POA-likes network. We should assume in advance that each miner node is reliable, at least in the grind new block, so as to ensure that the block reorganization of the network is an extremely low probability. Therefore, in the signet network model, which we build for community, I think two points are very important. 1. Choose honest and reliable partners to run miner nodes; 2. The miner program must be able to produce blocks stably in order. When a miner is not working, other nodes must can detecte the bad node within a period of time and put itself on the waiting list; Your reply reminds me that I should further improve the miner program to make the entire signet network more stable; Thank you again, RESPECT FOR YOU. |
|
|
|
did you create this as additional option for software developer ?
Yes, agree with you. For independent developers, regtest may be enough; but when multiple parties conduct joint debugging tests, a test network that can quickly produce blocks and fully match the characteristics of the Bitcoin main network is still very useful, and at least it will save a lot of Waiting time, time is wealth |
|
|
|
Obviously, the testnet's block production is unstable, and the old signet is not easy to get sBTC. What about testnet4? It is more stable than testnet3, and you can get new coins on a CPU. Also, in general, if you move your timestamps 20 minutes into the future, then you can mine blocks with minimal difficulty on testnet3 and testnet4, on a CPU. Also, when it comes to stability, it seems that some code from testnet4 is also applied into testnet3. And in that case, if you run a new client, then you can get a more stable testnet3. Another thing is that you can get sBTC from official signet, by executing some contracts with OP_CAT: https://delvingbitcoin.org/t/proof-of-work-based-signet-faucet/937/1Edit: Here you are: https://mempool.space/testnet4/block/0000000006612e6ecc73e171b07c754d566dad6a8c307298afbdc3723d8982e9As you can see, only 32 leading zero bits are enough, to get a new CPU-mined block in official testnet4. My miner was just lucky, and produced 37 zero bits instead. By the way, which code are you using for mining? Because when running signet with just OP_TRUE, I could get 50k sBTC, after a few minutes of grinding with Bitcoin Core. Which means, that you are probably running some unoptimized Python code in interactive mode or something, because getting a block with 20 leading zero bits every three minutes is something, which could fit the old Satoshi's prenet from 2008. Regarding the unfriendly aspects of testnet3/4, I have already replied ON https://bitcointalk.org/index.php?topic=5501712.0 About the mining code, I used the signet mine program provided by bitcoin core, which is written in python, but I made some modifications, and after complete testing, I will open source it. |
|
|
|
no new features have been added for the time being So, what is the purpose? Running testnet4 will give developers roughly the same outcome (and also the ability to mine their own blocks on their CPUs). I don’t think it is necessary to wait for 10 minutes. It depends, what do you want to test. In some cases, I even increased the time of the block into one hour or one day, for example to batch transactions from other chains, and summarize them every sometimes. And in case of a sidechain, something like "a block per three months" is also acceptable. Also, surprisingly, regtest seems to be more stable, than I previously thought. It cannot produce more than 43,200 blocks per two hours, which is one of the reasons, why I consider opening some regtest-like network to the outside world. If things are properly notarized, then it is possible to avoid "172,8 GB per two hours scenario", because nodes can start with regtest difficulty, then self-adjust to produce one share per 10 minutes, and then it doesn't look that bad. Glad to receive your reply. I can echo your questions on two aspects: 1. testnet3/4 is a completely open network. Sometimes, mining machines come in for testing, and block reorganization and transaction loss may occur. It is unfriendly to buider's development and joint debugging; in addition, the computing power of testnet3/4 will also fluctuate violently, which are unfriendly to buider's testing too. 2. In the world of blockchain, time is not based on physical time, but on block height. In the process of development and testing, especially for joint development, spending too much physical time waiting for a block to be high is not a good choice. If what I said is Inappropriate, please feel free to comment again |
|
|
|
Hi Everyone, I've already made a post in [Bitcoin Technical Support] Forum (URL: https://bitcointalk.org/index.php?topic=5501712.0), However, I think it's necessary for me to post it again in this forum so that more people can know about it. Obviously, the testnet's block production is unstable, and the old signet is not easy to get sBTC. In order to facilitate developers, I recently launched a new signet network, including: 1. Three block-mining nodes; 2. A browser based on mempool open source software; website is: https://signet.sathub.io3. An electrumx service; 4. An rpc and synchronization node; 5. signet faucet(will be open in the future); How they are connected can be seen in the documentation， https://docs.sathub.io/sathub-docs/connectThe main portal for the service is： https://sathub.ioEveryone is welcome to use it, it is free; it is currently in the trial operation stage, if you want to participate, please contact me via message box or reply directly and I will give you some sBTC; |
|
|
|
|
