 Show Posts
|
|
Pages: [1] 2 3 »
|
It is good to see BTCW is evolving. There is one concern though. The new Proof-of-Node concept looks nice but it not only adjusts the mining difficulty as expected in good purpost but also affects the node verifying hashes unintentionally, which will drastically affect block sync time. https://github.com/bitcoin-pow/BitcoinPoW/commit/bbc3cb8ce8206d9555b2a0d23c13ef5d90ff6172It would be best to take reasonable action before this hard fork takes effective at height 23333 in a week. I think the "k" value can be stored in the block nonce field with little code change and the side-effect to nodes will disappear (note currently nonce field is dead as filled with a fixed value always). Dev mentioned the impact will be minimal (in Satoshi-Pow channel) but doesn't seem so as the change algo needs heavier operation. Hope dev to test enough before final release or regret at the end. A week will be enough to test thoroughly. |
|
|
|
|
Is 256 going to be enough to distribute centralised mining to more miners? Maybe need 1024 (or 4096 or even more)?
Anyway the intention of adding 256 times PoW seems reasonable but it will introduces an undesirable impact on nodes as well (not miners) because when new blocks are synchronised each node also has to run that loop to verify the hash, which will logically slows down blockchain sync with a bit of pain when new node joins.
It may be more efficient if this is improved so only intend to change mining algo.
* It could be possible to put the loop index in the block header, nNonce which is now simply dead part as always set to 0xFEEDBEEF.
* This may be a right time to make this change along with the hard fork at #21111 rather than later time in case needed.
|
|
|
|
We are opened first mining pool! Now it is at experimental stage, but you can mine already, more info on our discord.
We also reach block 10.000, transactions are now unlocked!
Wow, passed 100,000 blocks now! Any good news? |
|
|
|
Have you applied for listing on Trust Wallet? Or still do we need to add custom token for BRC in Trust Wallet? |
|
|
|
Wow, great job! "Brownie Coins are backed by real brownies" and "Brownie Tokens on Binance chain are backed by Brownie Coins". Brownie Coins (42M) <-----> Brownie Tokens (99,000,000M) So is the plan 1. One Brownie Coin is equal to 2.3M Brownie Tokens or 2. 43,000,000M Brownie Tokens are backed by the max supply of Brownie Coins (1M BRC Token : 1 BRC Coin) and the remaining 56,000,000M Brownie Tokens for ICO? 3. Something else We are going to figure out how to link the two chains together but for now you can buy browniecoin on Pancake swap
Do you have plan to swap (or buy/sell) Brownie Coins (BRC Coin) vs Brownie Tokens (BRC Token) soon? |
|
|
|
We are still working on it. We have sent coin listing applications to major exchanges and still awaiting their response. One response were from Graviex who is asking for 0.1 BTC to list our coin. We will post an update once we get listed on any exchange. Thank you BTC3 Sounds good. Have you tried on Binance? It says the listing is free with donation. https://www.binance.com/en/support/faq/115000822512 |
|
|
|
Is there any node to connect? Explorer? It seems github source code does not include seed nodes at all. Maybe a real joke  |
|
|
|
|
Dev,
We need an official explorer please!
|
|
|
|
I found those nodes connecting to my node are in "banned" list automatically. I think it's because they are still in the wrong chain. If you are running a node from one of these, please run v1.0.2 and make sure to delete old chain info before restart. Also be careful not to delete your wallets. "address": "73.31.181.117/32",
"address": "91.152.210.102/32",
"address": "94.247.63.177/32",
"address": "95.84.178.175/32",
"address": "95.111.228.167/32",
"address": "195.238.117.169/32",
"address": "203.220.21.37/32",
"address": "206.116.249.47/32",
I will keep cleaning banned list so they can connect to the network. |
|
|
|
2021-04-09T03: 51: 01Z Socket recovery error Remote forcibly terminated an existing connection. (10054)
You could be more supportive to get help ;-) I don't think there are many people can help with that just the last line from your debug output. Could you copy more lines from the debug output? And please make sure old blockchain info is removed before restarting. Sorry if you have done so but there was no mention in your question. I think the directory is like: C:\Users\YourUserName\Appdata\Roaming\Bitcoin3 |
|
|
|
Dev download the working bitcoin3.conf
0 blocks and 0 connections, 6 weeks behind.
wallet 1.0.2
You need to make sure all directories/files to be removed except wallets from bitcoin3 directory. And add the available seed nodes and start bitcoin3-qt. For example my bitcoin3.conf is as following for your reference. addresstype=legacy
server=1
daemon=1
#gen=1
#genproclimit=-1
rpcbind=0.0.0.0
rpcuser=username-here
rpcpassword=pass-here
rpcallowip=127.0.0.1
listen=1
rest=1
onlynet=ipv4
dbcache=30
addnode=161.97.187.181
addnode=158.101.29.12
If nothing happens for several minutes after restarting bitcoin3-qt, then goto Help/Debug window/Information window, and click "Open" under "Debug log file" and show the last part of the output will be helpful to identify the problem. |
|
|
|
Sadly i am still not able to connect to the blockchain. I can offer the following: Dev can upload his blockchain (blocks, chainstate,...) as zip file to the Bitcoin3 website. After that i can download it and let the pool act as a node. The pool will most likely be there for a while so this would help to get all new people a working connection to the network. I can not allow unlimited nodes to connect to the pool, but there can be more than 15 connections at once. So the other nodes can sync and if someone is hosting a Bitcoin3 node in a datacentre, he could also allow in and outgoing traffic on the Bitcoin3 p2p port (not the RPC port, this port should ALWAYS be closed). The main error for not being connected is, as far as i can say, this error on the debug.log: ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 000000000000004130bdf143da15ee11d6d2f44e9c5d0b7f5624eb10c63b607c, bad-diffbits, incorrect proof of work (code 16)
Blockchain and chainstate have been uploaded to btc3 website. Hope we can have the pool act as a node for people to connect. Thanks Is this the right chain? "blocks": 6298 My node at 158.101.29.12 seems also running correctly now. Connected peers: '37.161.27.94:24517' '/Satoshi:1.0.2/' headers=6305/6307/6307" '194.50.15.119:2963' '/Satoshi:1.0.2/' headers=6305/6307/6307" '203.211.106.86:30904' '/Satoshi:1.0.2/' headers=6298/-1/-1" '46.138.178.248:36806' '/Satoshi:1.0.2/' headers=6306/6307/6307" '212.171.130.83:62569' '/Satoshi:1.0.2/' headers=6298/-1/-1" just to confirm: Block 6 308 ? Currently three connections on the pool, node is configured to allow inbound transaction, meaning new people can connect to the pools node and sync the blockchain. It seems the chain is moving now. I have 6 connections on my node and all nodes are from v1.0.2: Connected peers: "0: '212.171.130.83:62990' '/Satoshi:1.0.2/' headers=6313/6313/6313" "1: '161.97.187.181:49844' '/Satoshi:1.0.2/' headers=6313/6313/6313" "2: '194.50.15.119:2972' '/Satoshi:1.0.2/' headers=6313/6313/6313" "3: '37.161.27.94:24514' '/Satoshi:1.0.2/' headers=6313/6313/6313" "5: '203.211.106.86:22822' '/Satoshi:1.0.2/' headers=6313/6313/6313" "7: '46.138.178.248:36612' '/Satoshi:1.0.2/' headers=6313/6313/6313" |
|
|
|
Sadly i am still not able to connect to the blockchain. I can offer the following: Dev can upload his blockchain (blocks, chainstate,...) as zip file to the Bitcoin3 website. After that i can download it and let the pool act as a node. The pool will most likely be there for a while so this would help to get all new people a working connection to the network. I can not allow unlimited nodes to connect to the pool, but there can be more than 15 connections at once. So the other nodes can sync and if someone is hosting a Bitcoin3 node in a datacentre, he could also allow in and outgoing traffic on the Bitcoin3 p2p port (not the RPC port, this port should ALWAYS be closed). The main error for not being connected is, as far as i can say, this error on the debug.log: ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 000000000000004130bdf143da15ee11d6d2f44e9c5d0b7f5624eb10c63b607c, bad-diffbits, incorrect proof of work (code 16)
Blockchain and chainstate have been uploaded to btc3 website. Hope we can have the pool act as a node for people to connect. Thanks Is this the right chain? "blocks": 6298 My node at 158.101.29.12 seems also running correctly now. Connected peers: '37.161.27.94:24517' '/Satoshi:1.0.2/' headers=6305/6307/6307" '194.50.15.119:2963' '/Satoshi:1.0.2/' headers=6305/6307/6307" '203.211.106.86:30904' '/Satoshi:1.0.2/' headers=6298/-1/-1" '46.138.178.248:36806' '/Satoshi:1.0.2/' headers=6306/6307/6307" '212.171.130.83:62569' '/Satoshi:1.0.2/' headers=6298/-1/-1" |
|
|
|
Just noticed OP points to wrong github link. |
|
|
|
Setting up the new node with v1.0.2
New version doesn't seem to want to cooperate with other nodes set up here in the lab. Will need to be 100% working before posting here on OP.
Have you had any luck on the pool?
It seems still some nodes are running the old wallet, v1.0.0. The new wallet v1.0.2 is available and all nodes need to upgrade: * https://github.com/Bitcoin3-source/Bitcoin3-1.0.2/raw/main/bitcoin3-v1.0.2-windows.zip * source code : https://github.com/Bitcoin3-source/Bitcoin3.0Especially the current problem is that the main seed node is still running the old wallet and stuck at #1845. '136.144.171.201:30268' '/Satoshi:1.0.0/' headers=1845/-1/-1" This must be fixed so existing wallets and new people can join BTC3 network any time soon and we can move forward. |
|
|
|
cryptohamstr.com it is not a working pool but rather a fraudulent one since payments from it do not go
The pool requires more than 50 confirmations, so give it some more time and payouts will be working. This i no p2p pool where you get payed as soon as a block is mined. I did check the backend and there are no payouts yet. After doing a manually "sendtoaddress" test i receive the following info on the console: "error -4: fee estimation failed. fallbackfee is disabled. wait a few blocks or enable -fallbackfee." I remember that this also happened on BitcoinSV so i think in general we need to wait a bit more. I did put some hashing power on the pool in order to get more new blocks. I will look for the error again in a few hours. The pool has a "history" for all addresses mining Bitcoin3. So if the automatic payout wont pick up i will enable "fallbackfee" on the wallet and/or do manually payouts for the miners. As for the next "check" i will have a look on March 27, 2021, 04:30:00 PM forum time current time is March 27, 2021, 02:18:27 PM so i will post again in 2h. *edit* I did PM the DEV and told him about the error. In worst case i will manually payout the unpaid balance  Total Paid 2087.25000000 BTC3 but nothing made it to wallet so should I just wait or go back hashing Can you PM me your BTC3 address? So i will have a look for you, but i am quite sure that there is no TX ID for your payout so i can do a manual payout, this should be working. If there are any payout problems or any other issues, i will have a look and work on a solution 3QRwN5wm3sVKSfdB6x82tbJEnuoqGFeAxq Total Earned 298.65000000 BTC3 Can you confirm this and that you did not receive the payout even if the pool says it would have payed out? I think i have fixed future payout problems and i will manually payout "old" balances until March 27, 2021, 05:00:00 PM forum time. As soon as my test miner will automatically receive its payout all future payouts should be fine too Does Cryptohamstr.com support vardiff for BTC3? I would like to join mining. |
|
|
|
stuck at block 3004 now 2 hours behind, have not mined 1 coin yet lol, I think the big hash power locks it up so maybe start at high diff if you allow asics, working right now looks like, wallet staying up to date thats good
Hash in the pool just going higher and higher, https://cryptohamstr.com/site/minersBTC3, 1 miner -- 36.7 TH/s |
|
|
|
why can't we go through block 1845 yet?
I would not try yet, wait for the new wallet. It's currently at #3004 https://cryptohamstr.com/site/miningIf you are using v1.0.2, you may need to add nodes if it doesn't find nodes automatically: '158.101.29.12' '/Satoshi:1.0.2/' headers=2510/3004/3004" '35.215.69.197:30268' '/Satoshi:1.0.2/' headers=2510/2976/2976" '203.211.96.170:64733' '/Satoshi:1.0.2/' headers=2510/2989/2989" '176.9.9.210:61872' '/Satoshi:1.0.2/' headers=2910/3004/3004" '94.247.63.130:35814' '/Satoshi:1.0.2/' headers=1286/3004/3004" Or possibly you have banned some nodes, which should be cleared. |
|
|
|
|
