Search content
Sort by
Showing 20 of 224 results by JonHind
Re: [ANN][KURT] KURRENT - First Zerocoin that uses X11 algorithm - MANDATORY UPGRADE
Accumulating a lot of kurrent on cryptopia 
looks like moon in near future
Any other people feeling the same like me who are tired of these slow confirmation like today?
Pay a better transaction fee, get faster confirmation. Problem solved.
thats why weed need bitcoin unlimited .
Bitcoin is slow now
Re: Huobi host online event on BU, now looking for Core expert
28th March, Huobi hosted an online event in the evening titled Bitcoin scaling and its impact on price, featuring Jiang Zhuoer as the guest speaker. Jiang is well known for his strong support for Bitcoin Unlimited. The event attracted over 1,000 participants and Huobi is looking for a Core expert to answer questions from the Chinese investors on Bitcoin scaling.
http://news.8btc.com/huobi-host-online-event-on-bu-now-looking-for-core-expert
http://news.8btc.com/huobi-host-online-event-on-bu-now-looking-for-core-expert
I don't have any problem with bitcoin unlimited , hard fork should happen in near future so we can see how both of these goes .
Stopping BTU development with fud means that our current bitcoin infrastructure is afraid of them
bitcoin has competition and it is rising quickly , bitcoin has slowed and their has been no major development in the eco system .
Bitcoin Unlimited is the answer maybe but the clowns are clowns .
I am going into alts now as btc is down
Bitcoin Unlimited is the answer maybe but the clowns are clowns .
I am going into alts now as btc is down
Iconomi will buy back at no matter what the price is (subject to market value)
Everyone hold on tight and set their sell orders high ( above 0.01)
Everyone hold on tight and set their sell orders high ( above 0.01)
I will set my at 0.009 but still kudos to the team .
Nice money on iconomi , the devs are intelligent whooo !!!
Re: [ANN]💎[MBIT]💎🔹💎MBIT💎🔹💎MUSIC AND BOOKS SHARING PLATFORM🔹📚🎶[BETA LAUNCH]
Yes , I agree . The difficulty is a little off track and due to which mining blocks is difficult but I think this is the reason for constant increase in price to bring parity
between the mining cost and the price
I am still working on improving this re-target to suite to mining cost as this is leading to lots of mining hash getting up and difficulty snapping up like BOSS
between the mining cost and the price
I am still working on improving this re-target to suite to mining cost as this is leading to lots of mining hash getting up and difficulty snapping up like BOSS
Target timespan is 10 minutes
Target spacing is 5 minutes
As the algo is based 60% on Bitcoin algo . So we know that this problem would occur and the solution to that is slow increase in hash to stabilize the network
Target spacing is 5 minutes
As the algo is based 60% on Bitcoin algo . So we know that this problem would occur and the solution to that is slow increase in hash to stabilize the network
I think difficulty retargeting is messed up. In the last 24hrs only around 75 blocks are mined
Last 75 blocks (Time, Height, Difficulty):
Last 75 blocks (Time, Height, Difficulty):
Code:
[['2017-03-29 03:19:39' '871' '1650']
['2017-03-29 03:11:15' '870' '1650']
['2017-03-29 01:49:12' '869' '412']
['2017-03-29 01:49:07' '868' '412']
['2017-03-29 01:46:46' '867' '103']
['2017-03-29 01:46:09' '866' '103']
['2017-03-29 01:46:06' '865' '412']
['2017-03-29 01:16:22' '864' '412']
['2017-03-29 00:37:05' '863' '103']
['2017-03-29 00:36:37' '862' '103']
['2017-03-29 00:36:25' '861' '412']
['2017-03-29 00:34:08' '860' '412']
['2017-03-28 23:42:22' '859' '823']
['2017-03-28 23:22:40' '858' '823']
['2017-03-28 23:22:24' '857' '205']
['2017-03-28 23:22:05' '856' '205']
['2017-03-28 23:21:42' '855' '823']
['2017-03-28 23:21:29' '854' '823']
['2017-03-28 22:13:20' '853' '205']
['2017-03-28 22:13:18' '852' '205']
['2017-03-28 22:12:34' '851' '823']
['2017-03-28 21:39:31' '850' '823']
['2017-03-28 21:06:27' '849' '205']
['2017-03-28 21:06:20' '848' '205']
['2017-03-28 21:06:08' '847' '645']
['2017-03-28 20:55:59' '846' '645']
['2017-03-28 20:34:48' '845' '161']
['2017-03-28 20:34:38' '844' '161']
['2017-03-28 20:34:00' '843' '301']
['2017-03-28 20:28:43' '842' '301']
['2017-03-28 20:15:19' '841' '841']
['2017-03-28 20:09:32' '840' '841']
['2017-03-28 19:47:24' '839' '210']
['2017-03-28 19:46:10' '838' '210']
['2017-03-28 19:45:27' '837' '841']
['2017-03-28 19:43:11' '836' '841']
['2017-03-28 18:21:32' '835' '559']
['2017-03-28 18:16:23' '834' '559']
['2017-03-28 18:14:53' '833' '201']
['2017-03-28 18:11:57' '832' '201']
['2017-03-28 18:11:17' '831' '805']
['2017-03-28 16:23:47' '830' '805']
['2017-03-28 15:42:04' '829' '201']
['2017-03-28 15:41:59' '828' '201']
['2017-03-28 15:41:54' '827' '805']
['2017-03-28 15:33:11' '826' '805']
['2017-03-28 14:41:44' '825' '201']
['2017-03-28 14:41:13' '824' '201']
['2017-03-28 14:40:25' '823' '805']
['2017-03-28 14:23:33' '822' '805']
['2017-03-28 11:56:48' '821' '201']
['2017-03-28 11:55:49' '820' '201']
['2017-03-28 11:54:59' '819' '261']
['2017-03-28 11:53:55' '818' '261']
['2017-03-28 11:41:59' '817' '1047']
['2017-03-28 11:17:08' '816' '1047']
['2017-03-28 08:16:17' '815' '261']
['2017-03-28 08:16:09' '814' '261']
['2017-03-28 08:15:21' '813' '65']
['2017-03-28 08:14:34' '812' '65']
['2017-03-28 08:13:45' '811' '261']
['2017-03-28 07:37:46' '810' '261']
['2017-03-28 07:33:24' '809' '469']
['2017-03-28 07:18:30' '808' '469']
['2017-03-28 07:15:29' '807' '206']
['2017-03-28 07:11:32' '806' '206']
['2017-03-28 07:11:05' '805' '825']
['2017-03-28 06:58:06' '804' '825']
['2017-03-28 06:12:55' '803' '206']
['2017-03-28 06:11:55' '802' '206']
['2017-03-28 06:11:47' '801' '825']
['2017-03-28 04:25:54' '800' '825']
['2017-03-28 03:23:35' '799' '297']
['2017-03-28 03:20:09' '798' '297']
['2017-03-28 03:19:59' '797' '322']]
['2017-03-29 03:11:15' '870' '1650']
['2017-03-29 01:49:12' '869' '412']
['2017-03-29 01:49:07' '868' '412']
['2017-03-29 01:46:46' '867' '103']
['2017-03-29 01:46:09' '866' '103']
['2017-03-29 01:46:06' '865' '412']
['2017-03-29 01:16:22' '864' '412']
['2017-03-29 00:37:05' '863' '103']
['2017-03-29 00:36:37' '862' '103']
['2017-03-29 00:36:25' '861' '412']
['2017-03-29 00:34:08' '860' '412']
['2017-03-28 23:42:22' '859' '823']
['2017-03-28 23:22:40' '858' '823']
['2017-03-28 23:22:24' '857' '205']
['2017-03-28 23:22:05' '856' '205']
['2017-03-28 23:21:42' '855' '823']
['2017-03-28 23:21:29' '854' '823']
['2017-03-28 22:13:20' '853' '205']
['2017-03-28 22:13:18' '852' '205']
['2017-03-28 22:12:34' '851' '823']
['2017-03-28 21:39:31' '850' '823']
['2017-03-28 21:06:27' '849' '205']
['2017-03-28 21:06:20' '848' '205']
['2017-03-28 21:06:08' '847' '645']
['2017-03-28 20:55:59' '846' '645']
['2017-03-28 20:34:48' '845' '161']
['2017-03-28 20:34:38' '844' '161']
['2017-03-28 20:34:00' '843' '301']
['2017-03-28 20:28:43' '842' '301']
['2017-03-28 20:15:19' '841' '841']
['2017-03-28 20:09:32' '840' '841']
['2017-03-28 19:47:24' '839' '210']
['2017-03-28 19:46:10' '838' '210']
['2017-03-28 19:45:27' '837' '841']
['2017-03-28 19:43:11' '836' '841']
['2017-03-28 18:21:32' '835' '559']
['2017-03-28 18:16:23' '834' '559']
['2017-03-28 18:14:53' '833' '201']
['2017-03-28 18:11:57' '832' '201']
['2017-03-28 18:11:17' '831' '805']
['2017-03-28 16:23:47' '830' '805']
['2017-03-28 15:42:04' '829' '201']
['2017-03-28 15:41:59' '828' '201']
['2017-03-28 15:41:54' '827' '805']
['2017-03-28 15:33:11' '826' '805']
['2017-03-28 14:41:44' '825' '201']
['2017-03-28 14:41:13' '824' '201']
['2017-03-28 14:40:25' '823' '805']
['2017-03-28 14:23:33' '822' '805']
['2017-03-28 11:56:48' '821' '201']
['2017-03-28 11:55:49' '820' '201']
['2017-03-28 11:54:59' '819' '261']
['2017-03-28 11:53:55' '818' '261']
['2017-03-28 11:41:59' '817' '1047']
['2017-03-28 11:17:08' '816' '1047']
['2017-03-28 08:16:17' '815' '261']
['2017-03-28 08:16:09' '814' '261']
['2017-03-28 08:15:21' '813' '65']
['2017-03-28 08:14:34' '812' '65']
['2017-03-28 08:13:45' '811' '261']
['2017-03-28 07:37:46' '810' '261']
['2017-03-28 07:33:24' '809' '469']
['2017-03-28 07:18:30' '808' '469']
['2017-03-28 07:15:29' '807' '206']
['2017-03-28 07:11:32' '806' '206']
['2017-03-28 07:11:05' '805' '825']
['2017-03-28 06:58:06' '804' '825']
['2017-03-28 06:12:55' '803' '206']
['2017-03-28 06:11:55' '802' '206']
['2017-03-28 06:11:47' '801' '825']
['2017-03-28 04:25:54' '800' '825']
['2017-03-28 03:23:35' '799' '297']
['2017-03-28 03:20:09' '798' '297']
['2017-03-28 03:19:59' '797' '322']]
Re: [ANN]💎[MBIT]💎🔹💎MBIT💎🔹💎MUSIC AND BOOKS SHARING PLATFORM🔹💎📚🎶[POW]
UPDATE 1.0.5.X.C
Mbit Platform Launched
Mbit would be built upon the platform with bitcoin and mbit integration
Artists and Authors would be able to monotize their content online
http://www.mbitbooks.co/
Mbit Platform Launched
Mbit would be built upon the platform with bitcoin and mbit integration
Artists and Authors would be able to monotize their content online
http://www.mbitbooks.co/
All rights over the mbit platform is reserved by the mbit dev team
We would be releasing a Roadmap soon and would have a new update for it in coming days
Yes everything is looking good .
would be contributing my time to the project and the platform
PS :- Lets start with some serious work
Re: How many lines of code do I have to change to move the protocol to 10mb blocks?
One line (src/consensus/consensus.h):
Typically you want to adjust other parameters as well.
Code:
static const unsigned int MAX_BLOCK_BASE_SIZE = 1000000;
Typically you want to adjust other parameters as well.
yup this would set the parameter enough for the change because the more blocks are mined the blockchain transactions would increase over time
As we know, Jihan has too much power on the network, and apparently will soon have up to 80% of hashing rate once the new bitmain installations are deployed:
https://cointimes.tech/2017/03/statenationattack/
80% of the network controlled by a single entity with a very clear agenda. How can you call this decentralized with a straight face? how did satoshi didn't see this coming?
Anyway, the minority chain will obviously get crushed so I don't see any other way out but to change the PoW and render Jihan's monopoly useless.
We will still have the better devs, the problem is, we will have less hashing power.
At that point it all comes down to what the market will value: The better software with less hashing power under a new PoW algo, or the lesser devs with a ton of hashing power (but all concentrated in the hands of the same entity, which doesn't seem very safe regardless of the big hashing power, it would basically be 100% JihanCoin)
We'll see.
Anyway, my main point was: We change to another PoW algo. This makes sense short term for the reasons described above, but what about long term?
Doesn't a new algo create a new arms race to create the new mining machines that will create the new Jihan Wu's? And it will be in China, since they have the cheapest electricity.
So we have a constant here... the cheap electricity of china, that is the key that will keep generating chinese monopolies on a long enough timeline after a PoW algo change.
What can be done about this? Maybe something can be done to not allow a % higher than X inside the same area?
Can the IP's of the mining farms be blocked after X % is exceeded? maybe adjust depending on the electricity of the location of the miners?
anyway I guess IPs are useless nowadays due VPN and whatnot.
What is clear is we need something to avoid massive monopolies to be formed. Monopolies are never good for obvious reasons. We need something to force mining activities to be more widespread and not everything happening in china.
Less hashing power but more widespread mining operations are safer. Similarly, less nodes spread all over the world are safer than a million nodes inside a Coinbase bunker.
I don't know what the f*ck can be done, but the problem is obvious: china will always have the hedge due the ideal mining circumstances: cheap electricity and cheap production of the machines.
https://cointimes.tech/2017/03/statenationattack/
Quote
This mining facility by Bitmain in China (main supporter of BU) will single handedly have 80% hashing power overnight.
80% of the network controlled by a single entity with a very clear agenda. How can you call this decentralized with a straight face? how did satoshi didn't see this coming?
Anyway, the minority chain will obviously get crushed so I don't see any other way out but to change the PoW and render Jihan's monopoly useless.
We will still have the better devs, the problem is, we will have less hashing power.
At that point it all comes down to what the market will value: The better software with less hashing power under a new PoW algo, or the lesser devs with a ton of hashing power (but all concentrated in the hands of the same entity, which doesn't seem very safe regardless of the big hashing power, it would basically be 100% JihanCoin)
We'll see.
Anyway, my main point was: We change to another PoW algo. This makes sense short term for the reasons described above, but what about long term?
Doesn't a new algo create a new arms race to create the new mining machines that will create the new Jihan Wu's? And it will be in China, since they have the cheapest electricity.
So we have a constant here... the cheap electricity of china, that is the key that will keep generating chinese monopolies on a long enough timeline after a PoW algo change.
What can be done about this? Maybe something can be done to not allow a % higher than X inside the same area?
Can the IP's of the mining farms be blocked after X % is exceeded? maybe adjust depending on the electricity of the location of the miners?
anyway I guess IPs are useless nowadays due VPN and whatnot.
What is clear is we need something to avoid massive monopolies to be formed. Monopolies are never good for obvious reasons. We need something to force mining activities to be more widespread and not everything happening in china.
Less hashing power but more widespread mining operations are safer. Similarly, less nodes spread all over the world are safer than a million nodes inside a Coinbase bunker.
I don't know what the f*ck can be done, but the problem is obvious: china will always have the hedge due the ideal mining circumstances: cheap electricity and cheap production of the machines.
I agree , but now I accept the BTU AND BTC slit , lets see where this goes in future .
Bitcoin transactions have slowed over the past year and their is a lot of back log in transaction which is not good for business
so supporting roger ver idea but still looking the bandwagon of BTU is filled with noobs and clowns
What happened with Bitcoin 5 years ago is happening with Bitcoin Plus now. It's a great coin and deserves every bit of what's happening.
Looks like pump to me but I am no expert.Anyone who buys at this price has only themselves to blame if the price drops back to where it started.XBC has been on poloniex for years now trading at less than .001btc and there is NO legitimate reason for it to suddenly jump almost 2000% in two days.
I think you sold your coins to early ??