[ANN] Alterdot(ADOT), Web3 using Blockchain and IPFS, CPU Mining, Masternodes

[Enth]

Won't sync...

[cryptomaxsun]

Won't sync...

bitcreds.conf
addnode=198.98.111.248
addnode=103.94.185.6
addnode=81.162.194.236
addnode=46.38.238.142
addnode=193.187.183.15
addnode=198.98.111.253
addnode=176.36.154.195

https://explorer.bitcreds.org/network

[Enth]

Won't sync...

bitcreds.conf
addnode=198.98.111.248
addnode=103.94.185.6
addnode=81.162.194.236
addnode=46.38.238.142
addnode=193.187.183.15
addnode=198.98.111.253
addnode=176.36.154.195

https://explorer.bitcreds.org/network

it's not working. I have 10 active peers, but download don't start

in log i have:

Code:

2020-12-20 08:03:57 CMasternodeSync::ProcessTick -- nTick 211 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2020-12-20 08:04:02 CMasternodeSync::CheckNodeHeight -- skipping peer, who announced more headers than we have blocks currently, nHeight=0, nSyncHeight=964702, peer=1
2020-12-20 08:04:02 CMasternodeSync::CheckNodeHeight -- skipping peer, who announced more headers than we have blocks currently, nHeight=0, nSyncHeight=964702, peer=2
2020-12-20 08:04:02 CMasternodeSync::CheckNodeHeight -- skipping peer, who announced more headers than we have blocks currently, nHeight=0, nSyncHeight=964702, peer=3
2020-12-20 08:04:02 CMasternodeSync::CheckNodeHeight -- skipping peer, who announced more headers than we have blocks currently, nHeight=0, nSyncHeight=964702, peer=4
2020-12-20 08:04:02 CMasternodeSync::CheckNodeHeight -- skipping peer, who announced more headers than we have blocks currently, nHeight=0, nSyncHeight=964702, peer=5
2020-12-20 08:04:02 CMasternodeSync::CheckNodeHeight -- skipping peer, who announced more headers than we have blocks currently, nHeight=0, nSyncHeight=964702, peer=6
2020-12-20 08:04:02 CMasternodeSync::CheckNodeHeight -- skipping peer, who announced more headers than we have blocks currently, nHeight=0, nSyncHeight=964702, peer=7
2020-12-20 08:04:02 CMasternodeSync::CheckNodeHeight -- skipping peer, who announced more headers than we have blocks currently, nHeight=0, nSyncHeight=964702, peer=8
2020-12-20 08:04:02 CMasternodeSync::CheckNodeHeight -- skipping peer, who announced more headers than we have blocks currently, nHeight=0, nSyncHeight=964702, peer=9
2020-12-20 08:04:02 CMasternodeSync::CheckNodeHeight -- skipping peer, who announced more headers than we have blocks currently, nHeight=0, nSyncHeight=964702, peer=10
2020-12-20 08:04:03 CMasternodeSync::ProcessTick -- nTick 217 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000

[cryptomaxsun]

Won't sync...

bitcreds.conf
addnode=198.98.111.248
addnode=103.94.185.6
addnode=81.162.194.236
addnode=46.38.238.142
addnode=193.187.183.15
addnode=198.98.111.253
addnode=176.36.154.195

https://explorer.bitcreds.org/network

it's not working. I have 10 active peers, but download don't start

in log i have:

Code:

2020-12-20 08:03:57 CMasternodeSync::ProcessTick -- nTick 211 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2020-12-20 08:04:02 CMasternodeSync::CheckNodeHeight -- skipping peer, who announced more headers than we have blocks currently, nHeight=0, nSyncHeight=964702, peer=1
2020-12-20 08:04:02 CMasternodeSync::CheckNodeHeight -- skipping peer, who announced more headers than we have blocks currently, nHeight=0, nSyncHeight=964702, peer=2
2020-12-20 08:04:02 CMasternodeSync::CheckNodeHeight -- skipping peer, who announced more headers than we have blocks currently, nHeight=0, nSyncHeight=964702, peer=3
2020-12-20 08:04:02 CMasternodeSync::CheckNodeHeight -- skipping peer, who announced more headers than we have blocks currently, nHeight=0, nSyncHeight=964702, peer=4
2020-12-20 08:04:02 CMasternodeSync::CheckNodeHeight -- skipping peer, who announced more headers than we have blocks currently, nHeight=0, nSyncHeight=964702, peer=5
2020-12-20 08:04:02 CMasternodeSync::CheckNodeHeight -- skipping peer, who announced more headers than we have blocks currently, nHeight=0, nSyncHeight=964702, peer=6
2020-12-20 08:04:02 CMasternodeSync::CheckNodeHeight -- skipping peer, who announced more headers than we have blocks currently, nHeight=0, nSyncHeight=964702, peer=7
2020-12-20 08:04:02 CMasternodeSync::CheckNodeHeight -- skipping peer, who announced more headers than we have blocks currently, nHeight=0, nSyncHeight=964702, peer=8
2020-12-20 08:04:02 CMasternodeSync::CheckNodeHeight -- skipping peer, who announced more headers than we have blocks currently, nHeight=0, nSyncHeight=964702, peer=9
2020-12-20 08:04:02 CMasternodeSync::CheckNodeHeight -- skipping peer, who announced more headers than we have blocks currently, nHeight=0, nSyncHeight=964702, peer=10
2020-12-20 08:04:03 CMasternodeSync::ProcessTick -- nTick 217 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000

Last version?
does not sync at all?
upload bootstrap - https://github.com/Bitcreds/Bitcreds/releases/tag/v1.7.0.0

[Enth]

Won't sync...

bitcreds.conf
addnode=198.98.111.248
addnode=103.94.185.6
addnode=81.162.194.236
addnode=46.38.238.142
addnode=193.187.183.15
addnode=198.98.111.253
addnode=176.36.154.195

https://explorer.bitcreds.org/network

it's not working. I have 10 active peers, but download don't start

in log i have:

Code:

2020-12-20 08:03:57 CMasternodeSync::ProcessTick -- nTick 211 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2020-12-20 08:04:02 CMasternodeSync::CheckNodeHeight -- skipping peer, who announced more headers than we have blocks currently, nHeight=0, nSyncHeight=964702, peer=1
2020-12-20 08:04:02 CMasternodeSync::CheckNodeHeight -- skipping peer, who announced more headers than we have blocks currently, nHeight=0, nSyncHeight=964702, peer=2
2020-12-20 08:04:02 CMasternodeSync::CheckNodeHeight -- skipping peer, who announced more headers than we have blocks currently, nHeight=0, nSyncHeight=964702, peer=3
2020-12-20 08:04:02 CMasternodeSync::CheckNodeHeight -- skipping peer, who announced more headers than we have blocks currently, nHeight=0, nSyncHeight=964702, peer=4
2020-12-20 08:04:02 CMasternodeSync::CheckNodeHeight -- skipping peer, who announced more headers than we have blocks currently, nHeight=0, nSyncHeight=964702, peer=5
2020-12-20 08:04:02 CMasternodeSync::CheckNodeHeight -- skipping peer, who announced more headers than we have blocks currently, nHeight=0, nSyncHeight=964702, peer=6
2020-12-20 08:04:02 CMasternodeSync::CheckNodeHeight -- skipping peer, who announced more headers than we have blocks currently, nHeight=0, nSyncHeight=964702, peer=7
2020-12-20 08:04:02 CMasternodeSync::CheckNodeHeight -- skipping peer, who announced more headers than we have blocks currently, nHeight=0, nSyncHeight=964702, peer=8
2020-12-20 08:04:02 CMasternodeSync::CheckNodeHeight -- skipping peer, who announced more headers than we have blocks currently, nHeight=0, nSyncHeight=964702, peer=9
2020-12-20 08:04:02 CMasternodeSync::CheckNodeHeight -- skipping peer, who announced more headers than we have blocks currently, nHeight=0, nSyncHeight=964702, peer=10
2020-12-20 08:04:03 CMasternodeSync::ProcessTick -- nTick 217 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000

Last version?
does not sync at all?
upload bootstrap - https://github.com/Bitcreds/Bitcreds/releases/tag/v1.7.0.0

ok, now its working! How to import Credits wallet to Bitcreds?

[cryptomaxsun]

put the file wallet.ddat  in the folder with the blockchain.
don't forget to do backup.

[Enth]

put the file wallet.ddat  in the folder with the blockchain.
don't forget to do backup.

thanks! all is work!

[andrew2k]

Hello people, here's some news regarding the project.

Bitcreds will undergo a process of upgrade both visually as well as functionally. As mentioned in the updated thread title we will soon offer as a service the possibility to register IPFS content on our Blockchain Domain Name System (BDNS). This process will imply burning of coins and higher rewards for miners.

The change of our mining algorithm to Argon2d16000 in 4 days will imply an advantage for CPU mining and a period of time when wallet mining should be the norm. The length of this period depends on how fast standalone miners and pools adopt Argon2d16000.

The BDNS is our main focus for the upcoming period. The next next big release, v1.8, will include the BDNS and together with it we will release our browser extension. Due to the recent integration of IPFS into the Brave browser this will streamline the user experience of anyone wishing to get a feel of the decentralized web.

This project has been taken over by community members a while ago and we plan on maintaining this community-involved development process. Stay in touch for more information and rewarded tasks, you can find us on Discord or here.

v1.7.1 is also here with some small updates, it rejects all peers of v1.6.1 and previous versions.

https://github.com/Bitcreds/Bitcreds/releases/tag/v1.7.1.0

[andrew2k]

In less than 5 hours from now, at 6 PM UTC, we will make the switch to Argon2d16000 so prepare your wallets for mining as it will be the only way to mine Bitcreds after the hard fork. Expect your mining speeds to drop by up to 100x in comparison to Argon2d250, the algorithm currently in use.

Since this is a hard fork and taking precautions is recommended I advise not to send any significant transactions until tomorrow just to make sure you're on the right chain and the network is running smoothly.

If you like in-wallet CPU mining or you just like the stock, give it a go .

[maxiandr]

.

[GoodZilla]

How to mine from wallet on Mac OSX?
PS: there is no peers connecting

[TronQuix]

In less than 5 hours from now, at 6 PM UTC, we will make the switch to Argon2d16000 so prepare your wallets for mining as it will be the only way to mine Bitcreds after the hard fork. Expect your mining speeds to drop by up to 100x in comparison to Argon2d250, the algorithm currently in use.

Since this is a hard fork and taking precautions is recommended I advise not to send any significant transactions until tomorrow just to make sure you're on the right chain and the network is running smoothly.

If you like in-wallet CPU mining or you just like the stock, give it a go .

I like the stock!

Also if you need any help with anything let me know! Could be a fun project!

[minerja]

In less than 5 hours from now, at 6 PM UTC, we will make the switch to Argon2d16000 so prepare your wallets for mining as it will be the only way to mine Bitcreds after the hard fork. Expect your mining speeds to drop by up to 100x in comparison to Argon2d250, the algorithm currently in use.

Since this is a hard fork and taking precautions is recommended I advise not to send any significant transactions until tomorrow just to make sure you're on the right chain and the network is running smoothly.

If you like in-wallet CPU mining or you just like the stock, give it a go .

Hi
Would love to give it a go, BUT downloaded wallet, clean install, ZERO connections...
Any ideas?

[andrew2k]

In less than 5 hours from now, at 6 PM UTC, we will make the switch to Argon2d16000 so prepare your wallets for mining as it will be the only way to mine Bitcreds after the hard fork. Expect your mining speeds to drop by up to 100x in comparison to Argon2d250, the algorithm currently in use.

Since this is a hard fork and taking precautions is recommended I advise not to send any significant transactions until tomorrow just to make sure you're on the right chain and the network is running smoothly.

If you like in-wallet CPU mining or you just like the stock, give it a go .

Hi
Would love to give it a go, BUT downloaded wallet, clean install, ZERO connections...
Any ideas?

Synchronizing from zero takes quite a while even with enough connections so I recommend using the latest bootstrap here https://github.com/Bitcreds/Bitcreds/releases/tag/v1.7.0.0, you have instructions as well.

If you want to synchronize from scratch anyway you can connect to some of the nodes listed here https://explorer.bitcreds.org/network. The console command used for adding nodes is addnode <ip> add.

[minerja]

In less than 5 hours from now, at 6 PM UTC, we will make the switch to Argon2d16000 so prepare your wallets for mining as it will be the only way to mine Bitcreds after the hard fork. Expect your mining speeds to drop by up to 100x in comparison to Argon2d250, the algorithm currently in use.

Since this is a hard fork and taking precautions is recommended I advise not to send any significant transactions until tomorrow just to make sure you're on the right chain and the network is running smoothly.

If you like in-wallet CPU mining or you just like the stock, give it a go .

Hi
Would love to give it a go, BUT downloaded wallet, clean install, ZERO connections...
Any ideas?

Synchronizing from zero takes quite a while even with enough connections so I recommend using the latest bootstrap here https://github.com/Bitcreds/Bitcreds/releases/tag/v1.7.0.0, you have instructions as well.

If you want to synchronize from scratch anyway you can connect to some of the nodes listed here https://explorer.bitcreds.org/network. The console command used for adding nodes is addnode <ip> add.

Hi,
I'm using wallet 1.7.1.0 and have those nodes, but still zero connections....should i be using wallet 1.7.0.0?

[mrankin]

In less than 5 hours from now, at 6 PM UTC, we will make the switch to Argon2d16000 so prepare your wallets for mining as it will be the only way to mine Bitcreds after the hard fork. Expect your mining speeds to drop by up to 100x in comparison to Argon2d250, the algorithm currently in use.

Since this is a hard fork and taking precautions is recommended I advise not to send any significant transactions until tomorrow just to make sure you're on the right chain and the network is running smoothly.

If you like in-wallet CPU mining or you just like the stock, give it a go .

Hi
Would love to give it a go, BUT downloaded wallet, clean install, ZERO connections...
Any ideas?

Synchronizing from zero takes quite a while even with enough connections so I recommend using the latest bootstrap here https://github.com/Bitcreds/Bitcreds/releases/tag/v1.7.0.0, you have instructions as well.

If you want to synchronize from scratch anyway you can connect to some of the nodes listed here https://explorer.bitcreds.org/network. The console command used for adding nodes is addnode <ip> add.

Hi,
I'm using wallet 1.7.1.0 and have those nodes, but still zero connections....should i be using wallet 1.7.0.0?

V1.7.1.0 is the right version to use. If you have no nodes it maybe that your node's IP address is banned as myself and others manually banned quite a few older nodes. For further support, please post in the the #support channel of our Discord.

[mrankin]

Bitcreds will be undergoing some updates and improvements,  both visually as well as functionally. Bitcreds will soon offer as a service the possibility to register IPFS (InterPlanetary File System) content on our Blockchain Domain Name System (BDNS). This process will imply burning of coins and higher rewards for miners.

The reccent change of our mining algorithm to Argon2d16000 allows an advantage for CPU mining.

The BDNS is our main focus for the next pahse of development. In the next next big release (v1., we will include the BDNS along with our browser extension. Due to the recent integration of IPFS into the Brave browser this will streamline the user experience of anyone wanting to get a feel for the decentralized web.

This project was been taken over by community members a while ago and we plan on maintaining this community involved development process. Stay in touch with us on Discord for more information and rewarded tasks.

v1.7.1 is also here with some small updates, it rejects all peers of v1.6.1 and older versions.
https://github.com/Bitcreds/Bitcreds/releases/tag/v1.7.1.0

[mrankin]

We've updated the rewards structure on the website to reflect the changes we've made as of v1.7.1 to provide more funds for the future development of Bitcreds and also to reduce the total BCRS issued per block over time.

We're likely to hit block 1,000,000 in a few days which will see a couple of changes. Firstly, the block times will change from 128 seconds to 360 Seconds. Secondly, the block rewards will change as set out below (and in the OP of this thread) which will provide more funds for the future development of Bitcreds.

Both of these changes will reduce the total BCRS issued per day.

[TronQuix]

We've updated the rewards structure on the website to reflect the changes we've made as of v1.7.1 to provide more funds for the future development of Bitcreds and also to reduce the total BCRS issued per block over time.

We're likely to hit block 1,000,000 in a few days which will see a couple of changes. Firstly, the block times will change from 128 seconds to 360 Seconds. Secondly, the block rewards will change as set out below (and in the OP of this thread) which will provide more funds for the future development of Bitcreds.

Both of these changes will reduce the total BCRS issued per day.

Hey there, old CRDS user here, how do I redeem BCRS with CRDS? I have my old CRDS wallet still.

[mrankin]

Hey there, old CRDS user here, how do I redeem BCRS with CRDS? I have my old CRDS wallet still.

Just sync a new Bitcreds wallet with the network. Once done, shut down the wallet and replace the Bitcreds wallet.dat with your old Credits wallet.dat.

The addresses and chain is the same so all ald CRDS are still valid on the Bitrcreds chain.