metamorphin
Legendary
Offline
Activity: 1106
Merit: 1004
No risk, no fun!
|
 |
August 24, 2016, 06:41:47 PM Last edit: August 24, 2016, 08:05:31 PM by metamorphin |
|
We had today a meeting. I only wanna inform you, that Bitsend-dev will at home today evening and look over the network. He is on the road to his office! :-) Try to use only connect=85.214.68.75 so long till he is back.
Greetz Steve
|
|
|
|
|
Limx Dev (OP)
Copper Member
Legendary
Offline
Activity: 2352
Merit: 1348
|
 |
August 24, 2016, 07:45:41 PM Last edit: August 24, 2016, 09:14:20 PM by Limx Dev |
|
ANN UPDATE 1.1.0.0. Mandatory Updatehttps://github.com/LIMXTEC/BitSend/releases/tag/BSD1100Update BitSend 1.1.0.0Hardfork-Change Masternodes from 5000 BSD to 25.000 BSD -Change Block size up to 10 MB KB (4 MB) -Change TX size up to 250 KB (100 KB) + 1800 TXs Softfork Block 239.000-Add Dual KGW3 with Diffbreak -Change Blocktime to 3 min (6min) -Change Reward to 25 BSD(50 BSD) -change COINBASE_MATURITY to 288 (25) Block 240.000 Change Algo Hash to X17+ (not compatible to X17) DOWNLOAD https://github.com/LIMXTEC/BitSend/releases/tag/BSD1100Bounty for Linux Wallet or MAC Wallet 250 BSD I have disable the MASTERNODE_PAYMENTS_ENFORCEMENT for this update in the next days. Best Regards Christian No this Explorer works correct. I have enable bitsend diffbreak now.
Please use only the new Wallet. 1.1.0.0. the old wallets pays a wrong masternode amount for old 5000 BSD Masternodes.
It is possible that the wallet jump to the wrong chain!
Please use in bitsend.conf.
connect=85.214.68.75 connect=37.120.190.76 #(No addnode !)(Temporary)
Here is the correct chain. https://dl.dropboxusercontent.com/u/21000833/Bitsend/Chain/24-08-2016.zip 1. Delete the folder "blocks" and "chainstate" complete in your wallet folder. 2. Copy the new folder in your wallet folder. 3. Change your bitsend.conf connect=85.214.68.75 connect=37.120.190.76 4. Start your wallet.
Note: The Giveaway and weekly supporter is payed in the correct chain. Sorry for this trouble it is a big update for bitsend.
Best Regrads Christian
23:08:45  getblockhash 212448 23:08:45  0000000a8e0ba477f5d65cbe0c5de7fc50392f5ba84539ac143679e9948a0679
|
Bitcore BTX - a UTXO fork of Bitcoin - since 2017
|
|
|
|
hieu81
|
 |
August 25, 2016, 12:29:43 AM |
|
Nice to see your apdate! I downloaded and try this
|
|
|
|
|
|
hieu81
|
 |
August 25, 2016, 01:29:10 AM |
|
I try new update, but coin on date 24/08/2016 still pending Status: conflicted Date: 24/08/2016 03:23 From: unknown To: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Credit: 0.10 BSD Net amount: +0.10 BSD Transaction ID: a10f55b524e501b13540bb23aa38d6db7f5798be782599f6e3d266ffccbba8f7-000 Please check
|
|
|
|
|
techbytes
Legendary
Offline
Activity: 1694
Merit: 1054
Point. Click. Blockchain
|
 |
August 25, 2016, 01:42:29 AM |
|
ANN UPDATE 1.1.0.0. Mandatory Updatehttps://github.com/LIMXTEC/BitSend/releases/tag/BSD1100Update BitSend 1.1.0.0Hardfork-Change Masternodes from 5000 BSD to 25.000 BSD -Change Block size up to 10 MB KB (4 MB) -Change TX size up to 250 KB (100 KB) + 1800 TXs Softfork Block 239.000-Add Dual KGW3 with Diffbreak -Change Blocktime to 3 min (6min) -Change Reward to 25 BSD(50 BSD) -change COINBASE_MATURITY to 288 (25) Block 240.000 Change Algo Hash to X17+ (not compatible to X17) DOWNLOAD https://github.com/LIMXTEC/BitSend/releases/tag/BSD1100Bounty for Linux Wallet or MAC Wallet 250 BSD I have disable the MASTERNODE_PAYMENTS_ENFORCEMENT for this update in the next days. Best Regards Christian No this Explorer works correct. I have enable bitsend diffbreak now.
Please use only the new Wallet. 1.1.0.0. the old wallets pays a wrong masternode amount for old 5000 BSD Masternodes.
It is possible that the wallet jump to the wrong chain!
Please use in bitsend.conf.
connect=85.214.68.75 connect=37.120.190.76 #(No addnode !)(Temporary)
Here is the correct chain. https://dl.dropboxusercontent.com/u/21000833/Bitsend/Chain/24-08-2016.zip 1. Delete the folder "blocks" and "chainstate" complete in your wallet folder. 2. Copy the new folder in your wallet folder. 3. Change your bitsend.conf connect=85.214.68.75 connect=37.120.190.76 4. Start your wallet.
Note: The Giveaway and weekly supporter is payed in the correct chain. Sorry for this trouble it is a big update for bitsend.
Best Regrads Christian
23:08:45  getblockhash 212448 23:08:45  0000000a8e0ba477f5d65cbe0c5de7fc50392f5ba84539ac143679e9948a0679 Tried the above but still not getting on the same chain as https://chainz.cryptoid.info/bsd. Are you sure that block explorer is on the right chain as it hasn't move for over a day? -tb-
|
|
|
|
|
MasoVa
|
 |
August 25, 2016, 03:49:47 AM |
|
yes maybe not only me who's still not received bsd giveaway last week because i use bittrex and bsd wallet still on maintenance hope bsd wallet for personal user and exchange will fixed soon
|
|
|
|
|
|
stepmike
|
 |
August 25, 2016, 04:12:08 AM |
|
Here is the correct chain. https://dl.dropboxusercontent.com/u/21000833/Bitsend/Chain/24-08-2016.zip1. Delete the folder "blocks" and "chainstate" complete in your wallet folder. 2. Copy the new folder in your wallet folder. 3. Change your bitsend.conf connect=85.214.68.75 connect=37.120.190.76 4. Start your wallet.Note: The Giveaway and weekly supporter is payed in the correct chain. Sorry for this trouble it is a big update for bitsend. Best Regrads Christian 23:08:45  getblockhash 212448 23:08:45  0000000a8e0ba477f5d65cbe0c5de7fc50392f5ba84539ac143679e9948a0679 For me it work. Finally i received a weekly payment. Thanks.
|
|
|
|
|
|
hieu81
|
 |
August 25, 2016, 05:09:43 AM |
|
Please share to me bitsend.conf file I try this but until not work Here is the correct chain. https://dl.dropboxusercontent.com/u/21000833/Bitsend/Chain/24-08-2016.zip1. Delete the folder "blocks" and "chainstate" complete in your wallet folder. 2. Copy the new folder in your wallet folder. 3. Change your bitsend.conf connect=85.214.68.75 connect=37.120.190.76 4. Start your wallet.Note: The Giveaway and weekly supporter is payed in the correct chain. Sorry for this trouble it is a big update for bitsend. Best Regrads Christian 23:08:45  getblockhash 212448 23:08:45  0000000a8e0ba477f5d65cbe0c5de7fc50392f5ba84539ac143679e9948a0679 For me it work. Finally i received a weekly payment. Thanks.
|
|
|
|
|
Lariondos
Newbie
Offline
Activity: 12
Merit: 0
|
 |
August 25, 2016, 05:16:27 AM |
|
Sorry Christian, this is not the way crypto works. Your suggested chain has a very low hashrate, while the majority of miners is hashing at a different fork. You can't simply define your fork as the right one, you have to bring the majority of miners to consensus. Change the code accordingly and hope the miners update to this.
As far as I can see, the fork with the highest hashrate is currently at block 212747
getblockhash 212747 0000000002e95e21c399d5d72b5d8ae9371bda10eb35a67f888ac17c7517a873
hope you can fix this mess.
|
|
|
|
|
|
stepmike
|
 |
August 25, 2016, 05:17:43 AM |
|
Here is the correct chain. https://dl.dropboxusercontent.com/u/21000833/Bitsend/Chain/24-08-2016.zip 1. Delete the folder "blocks" and "chainstate" complete in your wallet folder. 2. Copy the new folder in your wallet folder. 3. Change your bitsend.conf connect=85.214.68.75 connect=37.120.190.76 4. Start your wallet.Note: The Giveaway and weekly supporter is payed in the correct chain. Sorry for this trouble it is a big update for bitsend. Best Regrads Christian 23:08:45  getblockhash 212448 23:08:45  0000000a8e0ba477f5d65cbe0c5de7fc50392f5ba84539ac143679e9948a0679 For me it work. Finally i received a weekly payment. Thanks. Please share to me bitsend.conf file I try this but until not work All is in green marked text. Do all the steps and everything will work. In bitsend.conf i have only connect=85.214.68.75 connect=37.120.190.76
|
|
|
|
|
|
hieu81
|
 |
August 25, 2016, 05:26:00 AM |
|
Thank for your help, but not work, I will try sync all, I have computer with win 7 32 bit Here is the correct chain. https://dl.dropboxusercontent.com/u/21000833/Bitsend/Chain/24-08-2016.zip 1. Delete the folder "blocks" and "chainstate" complete in your wallet folder. 2. Copy the new folder in your wallet folder. 3. Change your bitsend.conf connect=85.214.68.75 connect=37.120.190.76 4. Start your wallet.Note: The Giveaway and weekly supporter is payed in the correct chain. Sorry for this trouble it is a big update for bitsend. Best Regrads Christian 23:08:45  getblockhash 212448 23:08:45  0000000a8e0ba477f5d65cbe0c5de7fc50392f5ba84539ac143679e9948a0679 For me it work. Finally i received a weekly payment. Thanks. Please share to me bitsend.conf file I try this but until not work All is in green marked text. Do all the steps and everything will work. In bitsend.conf i have only connect=85.214.68.75 connect=37.120.190.76
|
|
|
|
|
|
stepmike
|
 |
August 25, 2016, 05:32:35 AM |
|
Thank for your help, but not work, I will try sync all, I have computer with win 7 32 bit
Do not sync from net you will be at wrong chain again.
|
|
|
|
|
|
|
|
stepmike
|
 |
August 25, 2016, 05:46:33 AM |
|
Yes, do that. P.S. Please, write answers after quoted text.
|
|
|
|
|
|
hieu81
|
 |
August 25, 2016, 06:08:08 AM |
|
Yes, do that. P.S. Please, write answers after quoted text. Thanks! Sorry about my mistake!
|
|
|
|
|
|
hieu81
|
 |
August 25, 2016, 07:10:43 AM |
|
Dear all friend Affter full sync with RPC PORT: 8800 P2P PORT: 8886 connect=85.214.68.75 connect=37.120.190.76 My wallet is ok! Thank to all!
|
|
|
|
|
Limx Dev (OP)
Copper Member
Legendary
Offline
Activity: 2352
Merit: 1348
|
 |
August 25, 2016, 09:58:45 AM |
|
ANN UPDATE 1.1.0.0. Mandatory Updatehttps://github.com/LIMXTEC/BitSend/releases/tag/BSD1100Update BitSend 1.1.0.0Hardfork-Change Masternodes from 5000 BSD to 25.000 BSD -Change Block size up to 10 MB KB (4 MB) -Change TX size up to 250 KB (100 KB) + 1800 TXs Softfork Block 239.000-Add Dual KGW3 with Diffbreak -Change Blocktime to 3 min (6min) -Change Reward to 25 BSD(50 BSD) -change COINBASE_MATURITY to 288 (25) Block 240.000 Change Algo Hash to X17+ (not compatible to X17) DOWNLOAD https://github.com/LIMXTEC/BitSend/releases/tag/BSD1100Bounty for Linux Wallet or MAC Wallet 250 BSD I have disable the MASTERNODE_PAYMENTS_ENFORCEMENT for this update in the next days. Best Regards Christian No this Explorer works correct. I have enable bitsend diffbreak now.
Please use only the new Wallet. 1.1.0.0. the old wallets pays a wrong masternode amount for old 5000 BSD Masternodes.
It is possible that the wallet jump to the wrong chain!
Please use in bitsend.conf.
connect=85.214.68.75 connect=37.120.190.76 #(No addnode !)(Temporary)
Here is the correct chain. https://dl.dropboxusercontent.com/u/21000833/Bitsend/Chain/24-08-2016.zip 1. Delete the folder "blocks" and "chainstate" complete in your wallet folder. 2. Copy the new folder in your wallet folder. 3. Change your bitsend.conf connect=85.214.68.75 connect=37.120.190.76 4. Start your wallet.
Note: The Giveaway and weekly supporter is payed in the correct chain. Sorry for this trouble it is a big update for bitsend.
Best Regrads Christian
23:08:45  getblockhash 212448 23:08:45  0000000a8e0ba477f5d65cbe0c5de7fc50392f5ba84539ac143679e9948a0679 Update{ "blocks" : 212682, "currentblocksize" : 0, "currentblocktx" : 0, "difficulty" : 0.22830040, "errors" : "", "genproclimit" : -1, "networkhashps" : 2297684, "pooledtx" : 0, "testnet" : false, "generate" : false, "hashespersec" : 0 }
|
Bitcore BTX - a UTXO fork of Bitcoin - since 2017
|
|
|
techbytes
Legendary
Offline
Activity: 1694
Merit: 1054
Point. Click. Blockchain
|
 |
August 25, 2016, 10:16:05 AM |
|
Cryptopools is on another chain eventhough I followed your instruction.... What gives?
{ "blocks" : 212800, "currentblocksize" : 14719, "currentblocktx" : 9, "difficulty" : 51.38960872, "errors" : "", "genproclimit" : -1, "networkhashps" : 673085526, "pooledtx" : 9, "testnet" : false, "generate" : false, "hashespersec" : 0
-tb-
Edit: Pool is connected to 15 peers all running version 1.1.0
|
|
|
|
Lariondos
Newbie
Offline
Activity: 12
Merit: 0
|
 |
August 25, 2016, 10:59:04 AM |
|
Looking at the hashrate, nearly no one is hashing at the "right" fork. There is nothing which can prevent anyone and my masternodes from hopping to the longer chain if nothing in the code prevents it!
|
|
|
|
|
|
|
|