[BTC2] Bitcoin 2, BTC Fork 1:1, PoS 🔥 Anonymous ⚡️Instant TX

[konstant111]

it's a great job what you're doing here, unfortunately not so happy to see the rate drop, but I think it's stabilizing in time, hard fork.

[1715485468]

1715485468

[john1010]

My BTC2 wallet got stuck syncing.. Im using the 2.1.4.0

[jackleszz]

My BTC2 wallet got stuck syncing.. Im using the 2.1.4.0

At what block number? Try restarting the wallet if you didn't already. If that doesn't help and the wallet shows that you have more than a few connections, then click to go to Tools - Information - and click the "delete local blockchain folders" button to let it resync.

Also currently uploading a blockchain snapshot file for faster syncing. This will be available at https://www.bitc2.org/snapshot-march-29-2019.zip after a couple of hours. If you choose to use that instead of the in-wallet resync button, read the ReadMe.txt first.

[quimbi777651]

My BTC2 wallet got stuck syncing.. Im using the 2.1.4.0

At what block number? Try restarting the wallet if you didn't already. If that doesn't help and the wallet shows that you have more than a few connections, then click to go to Tools - Information - and click the "delete local blockchain folders" button to let it resync.

Also currently uploading a blockchain snapshot file for faster syncing. This will be available at https://www.bitc2.org/snapshot-march-29-2019.zip after a couple of hours. If you choose to use that instead of the in-wallet resync button, read the ReadMe.txt first.

I used reindex blocks and it all worked for me. Can I use this method?

[jackleszz]

I used reindex blocks and it all worked for me. Can I use this method?

If it fixed your problem, of course.

[john1010]

My BTC2 wallet got stuck syncing.. Im using the 2.1.4.0

At what block number? Try restarting the wallet if you didn't already. If that doesn't help and the wallet shows that you have more than a few connections, then click to go to Tools - Information - and click the "delete local blockchain folders" button to let it resync.

Also currently uploading a blockchain snapshot file for faster syncing. This will be available at https://www.bitc2.org/snapshot-march-29-2019.zip after a couple of hours. If you choose to use that instead of the in-wallet resync button, read the ReadMe.txt first.

Done following your instruction, but none of them are working.. My wallet says, No block source available..

[jackleszz]

Done following your instruction, but none of them are working.. My wallet says, No block source available..

Ah so in other words you have no connections or peers. Try stopping the wallet, then deleting the peers.dat and banlist.dat files from Bitcoin 2 data folder.  Then start the wallet again. Could also be a networking problem on your computer, router or ISP if that and a reboot does not help.

[jackleszz]

Relating to peers, my wallet connected to network, but its synchronisation speed is low.
So, can you help me with peer list, that I can add more peer-nodes and help to increase my wallet synchronisation process, please.
Many thanks if you can help, because I don't usually open wallet, maybe only one time per two weeks, and it takes time to finish sync process.

You can find some peer IP addresses at https://www.whatsmydns.net/#A/seed.bitc2.org but those your wallet should be able to find automatically.
Can't really help speed that up if you're already past 100,000 blocks. When syncing automatically, Bitcoin 2 Core verifies that the blocks are valid instead of just trusting them and that is what takes time especially with a slow computer.
If you're not past 100,000 blocks, then downloading the snapshot I mentioned above would help.

[ClaimyMcClaim]

my masternode worked for a couple hours and then it stopped getting masternode rewards after minting a 0.6 reward

i restarted bitcoin2d and it says "staking status": "Staking Active", on the console with "bitcoin2-cli getinfo" but appears as missing on masternodes tab with an error "could not allocate txin"

in coin control i have 1000 btc2 locked and 1000.6 unlocked but i only have 1000 coins. is this normal?

it worked fine for a couple hours, why did it stop working after getting the 0.6 reward?

thanks

[jackleszz]

my masternode worked for a couple hours and then it stopped getting masternode rewards after minting a 0.6 reward

i restarted bitcoin2d and it says "staking status": "Staking Active", on the console with "bitcoin2-cli getinfo" but appears as missing on masternodes tab with an error "could not allocate txin"

in coin control i have 1000 btc2 locked and 1000.6 unlocked but i only have 1000 coins. is this normal?

it worked fine for a couple hours, why did it stop working after getting the 0.6 reward?

thanks

No that's not normal. Most likely you failed to lock it properly with the masternode.conf and then the 1000 staked and became immature and no longer equals 1000 and thus is no longer a valid masternode collateral amount. I take it that it is a new attempt at creating a masternode?
If the private key to that masternode BTC2 address is also in use at the web wallet or some other actively staking computer, then that would be the problem.

Even without doing anything wrong per se, it is also possible for the newly transferred 1000 BTC2 to stake before you get the chance to lock it with masternode.conf, if you waited for over an hour since the initial 1000 BTC2 transfer before doing that. You need to restart the wallet after changing masternode.conf for the lock to become effective.

You will need to redo the process of transferring 1000 BTC2 to another new address of yours and so on. (Remove the line at masternode.conf that you created, restart the local wallet and then go back to Step 1 of the guide at https://www.bitc2.org/bitcoin-2-masternode-guide).

[ClaimyMcClaim]

are there any stats available about how many coins have been claimed?

specifically how many addresses with more than 1000btc2 have not claimed yet?

are there any plans to limit the claim time for wallets with more than 1000btc or to limit the amount claimable per key? i.e. if you have more than 1k btc you can only claim 1k or 500 or whatever arbitrary amount.

other bitcoin forks suffer from constant dumping and have opted for limiting the claim window and/or limiting the amounts claimable, has btc2 considered improving its pumpamentals by reducing the unclaimed supply in this or other manner?

i would assume that what im proposing would require a hardfork so it should be "easier" to do it now that its only listed on a couple exchanges. (im talking out of my ass, i have no clue about the actual difficulty or even feasibility)

it wouldnt be fair to have whales dump on us when the price gets attractive; a couple of whales can fuck up the price badly so thats why i think focusing on big wallets would be more effective than just disabling claims for everyone.

[Hiromono]

are there any stats available about how many coins have been claimed?

specifically how many addresses with more than 1000btc2 have not claimed yet?

are there any plans to limit the claim time for wallets with more than 1000btc or to limit the amount claimable per key? i.e. if you have more than 1k btc you can only claim 1k or 500 or whatever arbitrary amount.

other bitcoin forks suffer from constant dumping and have opted for limiting the claim window and/or limiting the amounts claimable, has btc2 considered improving its pumpamentals by reducing the unclaimed supply in this or other manner?

i would assume that what im proposing would require a hardfork so it should be "easier" to do it now that its only listed on a couple exchanges. (im talking out of my ass, i have no clue about the actual difficulty or even feasibility)

it wouldnt be fair to have whales dump on us when the price gets attractive; a couple of whales can fuck up the price badly so thats why i think focusing on big wallets would be more effective than just disabling claims for everyone.

Whales are likely to have multiple addresses anyway and getting a whale on board would be far more important than getting a regular guy on board. So unlikely to differentiate between whales and others when deciding who can claim.

Earlier on this thread we talked about doing such a fork and it seemed people here welcomed it and yes, it would be easier now. We even thought of a way to do it without forced forking which would just make it harder but not impossible to claim BTC2.

It hasn't really been a priority lately because there hasn't been many claims that simply sold straight away after claiming lately. The claiming block height is over a year ago and only true hodlers are likely to remember their private keys of that time since they still have the same addresses. But a coinmarketcap listing could still let more of those people know that they have something to claim.

No actual stats have been compiled of how much has been claimed as it would take a lot of blockchain analysis by a program or human to do it but it is a minor %.

There are cons to stopping claims, such as perception about it of those that don't yet own BTC2 and keeping the supply unaffected would make our coin market cap look high and make it easier to be in the top 100 at coinmarketcap. The solution we are most likely to do would not affect this supply number. Then again Bitcoin private did a coinburn more than a month ago and yet coinmarketcap did not update their circulating supply, yet anyway.

[quimbi777651]

are there any stats available about how many coins have been claimed?

specifically how many addresses with more than 1000btc2 have not claimed yet?

are there any plans to limit the claim time for wallets with more than 1000btc or to limit the amount claimable per key? i.e. if you have more than 1k btc you can only claim 1k or 500 or whatever arbitrary amount.

other bitcoin forks suffer from constant dumping and have opted for limiting the claim window and/or limiting the amounts claimable, has btc2 considered improving its pumpamentals by reducing the unclaimed supply in this or other manner?

i would assume that what im proposing would require a hardfork so it should be "easier" to do it now that its only listed on a couple exchanges. (im talking out of my ass, i have no clue about the actual difficulty or even feasibility)

it wouldnt be fair to have whales dump on us when the price gets attractive; a couple of whales can fuck up the price badly so thats why i think focusing on big wallets would be more effective than just disabling claims for everyone.

Whales are likely to have multiple addresses anyway and getting a whale on board would be far more important than getting a regular guy on board. So unlikely to differentiate between whales and others when deciding who can claim.

Earlier on this thread we talked about doing such a fork and it seemed people here welcomed it and yes, it would be easier now. We even thought of a way to do it without forced forking which would just make it harder but not impossible to claim BTC2.

It hasn't really been a priority lately because there hasn't been many claims that simply sold straight away after claiming lately. The claiming block height is over a year ago and only true hodlers are likely to remember their private keys of that time since they still have the same addresses. But a coinmarketcap listing could still let more of those people know that they have something to claim.

No actual stats have been compiled of how much has been claimed as it would take a lot of blockchain analysis by a program or human to do it but it is a minor %.

There are cons to stopping claims, such as perception about it of those that don't yet own BTC2 and keeping the supply unaffected would make our coin market cap look high and make it easier to be in the top 100 at coinmarketcap. The solution we are most likely to do would not affect this supply number. Then again Bitcoin private did a coinburn more than a month ago and yet coinmarketcap did not update their circulating supply, yet anyway.

I do not like the idea of hard fork, but somehow it is necessary to protect oneself from dump on of coins, for example, by exchanges.

[jackleszz]

I do not like the idea of hard fork, but somehow it is necessary to protect oneself from dump on of coins, for example, by exchanges.

The best method we came up with, which would make it harder but not impossible to claim would probably suffice and it would be achievable with a soft fork and the exchanges listing BTC2 wouldn't even need to update their wallets.

It would take some careful planning or a lot of trial and error by exchanges to know which Bitcoin addresses could be used to claim BTC2, because most of their addresses probably aren't old enough.

Another plus side to stopping claims eventually is that then the bigger exchanges wouldn't need to worry about rewarding BTC2 balances of over a year ago to their users and thus it would be much easier for them to list BTC2.

[luvbeening]

any plant to get the support from hardware wallet like trezor or ledger nano?nowardays a lot of bitcoin hodlers might keep their bitcoin in hardware wallet,it will makes these hodlers  to claim their Btc2 on hardware wallet more easier without risk,and this will help a great adoption for Btc2.

POS is the trend and i beleive Btc2 actually do have a very good competation with others frok coins like Bitcoin Cash or BitcoinSV.

[quimbi777651]

I do not like the idea of hard fork, but somehow it is necessary to protect oneself from dump on of coins, for example, by exchanges.

The best method we came up with, which would make it harder but not impossible to claim would probably suffice and it would be achievable with a soft fork and the exchanges listing BTC2 wouldn't even need to update their wallets.

It would take some careful planning or a lot of trial and error by exchanges to know which Bitcoin addresses could be used to claim BTC2, because most of their addresses probably aren't old enough.

Another plus side to stopping claims eventually is that then the bigger exchanges wouldn't need to worry about rewarding BTC2 balances of over a year ago to their users and thus it would be much easier for them to list BTC2.

I really like the decision of the team.

[ClaimyMcClaim]

Earlier on this thread we talked about doing such a fork and it seemed people here welcomed it and yes, it would be easier now. We even thought of a way to do it without forced forking which would just make it harder but not impossible to claim BTC2.

The best method we came up with, which would make it harder but not impossible to claim would probably suffice and it would be achievable with a soft fork and the exchanges listing BTC2 wouldn't even need to update their wallets.

It would take some careful planning or a lot of trial and error by exchanges to know which Bitcoin addresses could be used to claim BTC2, because most of their addresses probably aren't old enough.

Another plus side to stopping claims eventually is that then the bigger exchanges wouldn't need to worry about rewarding BTC2 balances of over a year ago to their users and thus it would be much easier for them to list BTC2.

i wasnt aware of that, if it can be achieved without hardforking thats even better

[jackleszz]

any plant to get the support from hardware wallet like trezor or ledger nano?nowardays a lot of bitcoin hodlers might keep their bitcoin in hardware wallet,it will makes these hodlers  to claim their Btc2 on hardware wallet more easier without risk,and this will help a great adoption for Btc2.

POS is the trend and i beleive Btc2 actually do have a very good competation with others frok coins like Bitcoin Cash or BitcoinSV.

Looks like adding Trezor support is just a matter of contributing the configuration to their Github and waiting for them to approve it and do the rest. Although possibly we'll also need to configure and run one of their custom block explorers. So Trezor support seems likely to be coming.

[jackleszz]

A display bug introduced recently to the web wallet that hid the oldest two transactions in the transactions list was fixed today.

[konstant111]

Please developer more news on the project than you intend to deal with now, what's next, sincerely thank you