standards
|
|
January 11, 2018, 12:22:49 PM |
|
Bitcoin cash has outperformed most of the coins during this bullish market. Compared to other Bitcoin forks, BCH is unique and much better.
|
|
|
|
bitcoinPsycho
Legendary
Offline
Activity: 2618
Merit: 2369
$120000 in 2024 Confirmed
|
|
January 11, 2018, 12:28:29 PM |
|
seems the only way to promote this coin is to trash/badmouth/lie about others. and you trolls wonder why you have NO RESPECT. You are the bad apples of the crypto world. if bitcoin fail you fail
|
$100,000 BTC in one hour
|
|
|
svennnny
Member
Offline
Activity: 182
Merit: 17
|
|
January 11, 2018, 12:59:10 PM |
|
|
|
|
|
curt0
Newbie
Offline
Activity: 30
Merit: 0
|
|
January 11, 2018, 01:03:18 PM |
|
ya and if BTC the granddaddy of crypto dies..do you think this grease stain of an ALT with no usage will "MOON" lmao. Glad as hell I got to dump my free ones at 3600 after Conbase got done fookin around.
OMG you really are thick! nobody said btc is dying...old chain is old...slow..expensive...legacy is dying and to make it worse its infected with segwet...something nobody wants. so before infection... btc forked...it upgraded...it evolved... in order to keep up it had too...and look at the result...cheap,fast and soon private tx on-chain. What is it you want? you seem really lost...i feel sorry for you tbh. BCH is BTC It's amazing how biased and censored this forum has become. You are a hero member and the moderator gave you a negative trust because you criticized BTC. Same thing happened to me. BTC has no clothes.
|
|
|
|
curt0
Newbie
Offline
Activity: 30
Merit: 0
|
|
January 11, 2018, 01:06:39 PM |
|
ya and if BTC the granddaddy of crypto dies..do you think this grease stain of an ALT with no usage will "MOON" lmao. Glad as hell I got to dump my free ones at 3600 after Conbase got done fookin around.
meanwhile at /r/bitcoin/ https://i.imgur.com/bNWtaC3.jpgMichael Marquardt's (Theymos) photo should be on that North Korean flag. r/bitcoin is like the North Korean media, where any dissenting viewpoint is banned or censored.
|
|
|
|
pawel7777
Legendary
Offline
Activity: 2576
Merit: 1621
|
|
January 11, 2018, 01:15:17 PM |
|
The conference organizer, Moe Levin, earlier told Bitcoin.com that his company was working to get bitcoin cash or other digital assets with cheaper fees integrated into the ticketing system. He told the news site: "We wish this was easier, but no ticketing options exist which can handle large volumes of ticket sales, and transaction fees on the Bitcoin blockchain exceed $30 at certain times of the day." Not even funny anymore, that's just sad
|
| Duelbits | ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ | | TRY OUR UNIQUE GAMES! ◥ DICE ◥ MINES ◥ PLINKO ◥ DUEL POKER ◥ DICE DUELS | | | | █▀▀ █ █ █ █ █ █ █ █ █ █ █ █▄▄ | ███ ▀▀▀ ███ ▀▀▀ ███ ▀▀▀ ███ ▀▀▀ ███ ▀▀▀ ███ ▀▀▀ | ███ ▀▀▀ ███ ▀▀▀ ███ ▀▀▀ ███ ▀▀▀ ███ ▀▀▀ ███ ▀▀▀ | ███ ▀▀▀ ███ ▀▀▀ ███ ▀▀▀ ███ ▀▀▀ ███ ▀▀▀ ███ ▀▀▀ | ███ ▀▀▀ ███ ▀▀▀ ███ ▀▀▀ ███ ▀▀▀ ███ ▀▀▀ ███ ▀▀▀ | ███ ▀▀▀ ███ ▀▀▀ ███ ▀▀▀ ███ ▀▀▀ ███ ▀▀▀ ███ ▀▀▀ | | ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ KENONEW ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ | ▀▀█ █ █ █ █ █ █ █ █ █ █ █ ▄▄█ | | 10,000x MULTIPLIER | | ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ | | ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ |
[/tabl
|
|
|
fackthensa
Newbie
Offline
Activity: 16
Merit: 0
|
|
January 11, 2018, 02:01:46 PM |
|
BCH BFD $2730s = bargain I think tonight is the last time we see BCH under $3k & last time @$50bill right now 1 old btc gets you just over 5 new btc, this wont last long ... wth you waiting for?..... dump old btc for BCH ..do it...do it NOW https://m.popkey.co/9f5aeb/QlJ0y_s-200x150.gifNice pump and dump again mr Pumptits seems like there is no flippening weeee Your predictions seems to be so accurate u must be a pro trader dont come crying to him when you see BCH at 10k + enjoy buying a coffe for 30$
|
|
|
|
Cryptoneer
Jr. Member
Offline
Activity: 116
Merit: 7
|
|
January 11, 2018, 02:02:27 PM |
|
So, these new q-addresses, I can use them instead of the 1-addresses, right? Even from exchanges?
|
Så kan det gå, om CAPS LOCK är PÅ!
|
|
|
phuckit17
|
|
January 11, 2018, 02:18:29 PM |
|
Good Morning! https://t.co/7uAQx30Pin Looky what I found: —ACINQ, Blockstream, and Lightning Labs announced that a release candidate for the Lightning Network 1.0 was READY along with a successful cross-implementation test on Bitcoin mainnet. Could you please share your thoughts on what impact this could have on the Bitcoin network in the long run? Lightning Network will help Bitcoin and Litecoin scale. I'm very excited about this and looking forward to it being used by everyone very soon. Cross-chain atomic swaps will also make it very easy for people to interchangeably use Bitcoin and Litecoin. Have a pleasant Day.
|
|
|
|
rehydrogenated
|
|
January 11, 2018, 02:25:24 PM |
|
Bitcoin cash continues to amaze me. It's in the green amid a sea of red today. I have to admit I didn't want to follow this project at first, but the bitcoin community has shown that it has no interest in making bitcoin better. Maybe bitcoin cash has an opportunity to step in and be useful the way bitcoin was for too short a time.
|
|
|
|
curt0
Newbie
Offline
Activity: 30
Merit: 0
|
|
January 11, 2018, 02:32:10 PM |
|
Good Morning! https:/[Suspicious link removed]/7uAQx30Pin Looky what I found: —ACINQ, Blockstream, and Lightning Labs announced that a release candidate for the Lightning Network 1.0 was READY along with a successful cross-implementation test on Bitcoin mainnet. Could you please share your thoughts on what impact this could have on the Bitcoin network in the long run? Lightning Network will help Bitcoin and Litecoin scale. I'm very excited about this and looking forward to it being used by everyone very soon. Cross-chain atomic swaps will also make it very easy for people to interchangeably use Bitcoin and Litecoin. Have a pleasant Day. Bitcoin’s Lightning Network Will Likely Fail Due To Several Possible Reasons https://medium.com/@curt0/lightning-network-will-likely-fail-due-to-several-possible-reasons-336c6c47f049
|
|
|
|
hv_
Legendary
Offline
Activity: 2534
Merit: 1055
Clean Code and Scale
|
|
January 11, 2018, 02:35:13 PM |
|
Good Morning! https://t.co/7uAQx30Pin Looky what I found: —ACINQ, Blockstream, and Lightning Labs announced that a release candidate for the Lightning Network 1.0 was READY along with a successful cross-implementation test on Bitcoin mainnet. Could you please share your thoughts on what impact this could have on the Bitcoin network in the long run? Lightning Network will help Bitcoin and Litecoin scale. I'm very excited about this and looking forward to it being used by everyone very soon. Cross-chain atomic swaps will also make it very easy for people to interchangeably use Bitcoin and Litecoin. Have a pleasant Day. Cool - Get it done - make it ready - test it out! Really - make it good and figure out where its real use cases are and try to compete with simpler tech (BCH). BCH community is open to all theses good things and will not kill the good things - rather adopt it if working. But for now and the near future max on-chain capacity together with enough decentralization & known security and less attack surfaces is the way to go.
|
Carpe diem - understand the White Paper and mine honest. Fix real world issues: Check out b-vote.com The simple way is the genius way - Satoshi's Rules: humana veris _
|
|
|
f4
Member
Offline
Activity: 86
Merit: 10
|
|
January 11, 2018, 03:55:07 PM |
|
Good Morning! https:/[Suspicious link removed]/7uAQx30Pin Looky what I found: —ACINQ, Blockstream, and Lightning Labs announced that a release candidate for the Lightning Network 1.0 was READY along with a successful cross-implementation test on Bitcoin mainnet. Could you please share your thoughts on what impact this could have on the Bitcoin network in the long run? Lightning Network will help Bitcoin and Litecoin scale. I'm very excited about this and looking forward to it being used by everyone very soon. Cross-chain atomic swaps will also make it very easy for people to interchangeably use Bitcoin and Litecoin. Have a pleasant Day. Bitcoin’s Lightning Network Will Likely Fail Due To Several Possible Reasons https://medium.com/@curt0/lightning-network-will-likely-fail-due-to-several-possible-reasons-336c6c47f049Even with centralized payment channels and more regulation LN doesnt necessarily need to fail. People will use the most established and convenient system. https://www.youtube.com/watch?v=UYHFrf5ci_g
|
|
|
|
curt0
Newbie
Offline
Activity: 30
Merit: 0
|
|
January 11, 2018, 04:31:57 PM |
|
Good Morning! https:/[Suspicious link removed]/7uAQx30Pin Looky what I found: —ACINQ, Blockstream, and Lightning Labs announced that a release candidate for the Lightning Network 1.0 was READY along with a successful cross-implementation test on Bitcoin mainnet. Could you please share your thoughts on what impact this could have on the Bitcoin network in the long run? Lightning Network will help Bitcoin and Litecoin scale. I'm very excited about this and looking forward to it being used by everyone very soon. Cross-chain atomic swaps will also make it very easy for people to interchangeably use Bitcoin and Litecoin. Have a pleasant Day. Bitcoin’s Lightning Network Will Likely Fail Due To Several Possible Reasons https://medium.com/@curt0/lightning-network-will-likely-fail-due-to-several-possible-reasons-336c6c47f049Even with centralized payment channels and more regulation LN doesnt necessarily need to fail. People will use the most established and convenient system. https://www.youtube.com/watch?v=UYHFrf5ci_gBlockstream refuted bigger blocks because they didn't want centralization. Not only will LN be extremely centralized, it will be regulated by the government. Say goodbye to censorship-resistance, permission-less and trust-less. Without these, Visa is more "established and convenient" than LN.
|
|
|
|
svennnny
Member
Offline
Activity: 182
Merit: 17
|
|
January 11, 2018, 06:10:50 PM |
|
ya and if BTC the granddaddy of crypto dies..do you think this grease stain of an ALT with no usage will "MOON" lmao. Glad as hell I got to dump my free ones at 3600 after Conbase got done fookin around.
OMG you really are thick! nobody said btc is dying...old chain is old...slow..expensive...legacy is dying and to make it worse its infected with segwet...something nobody wants. so before infection... btc forked...it upgraded...it evolved... in order to keep up it had too...and look at the result...cheap,fast and soon private tx on-chain. What is it you want? you seem really lost...i feel sorry for you tbh. BCH is BTC It's amazing how biased and censored this forum has become. You are a hero member and the moderator gave you a negative trust because you criticized BTC. Same thing happened to me. BTC has no clothes. Haha couldn't Roger buy this forum ? Don't like it here feel free to join another forum
|
|
|
|
svennnny
Member
Offline
Activity: 182
Merit: 17
|
|
January 11, 2018, 06:24:17 PM |
|
Good Morning! https://t.co/7uAQx30Pin Looky what I found: —ACINQ, Blockstream, and Lightning Labs announced that a release candidate for the Lightning Network 1.0 was READY along with a successful cross-implementation test on Bitcoin mainnet. Could you please share your thoughts on what impact this could have on the Bitcoin network in the long run? Lightning Network will help Bitcoin and Litecoin scale. I'm very excited about this and looking forward to it being used by everyone very soon. Cross-chain atomic swaps will also make it very easy for people to interchangeably use Bitcoin and Litecoin. Have a pleasant Day. The Bcash trolls know it and do whatever they can to manipulate the market. But after all we can all see Bitcoin is king. When LN is operational we can expect Bcash to drop below 1K. You have been warned folks.
|
|
|
|
curt0
Newbie
Offline
Activity: 30
Merit: 0
|
|
January 11, 2018, 07:12:36 PM |
|
ya and if BTC the granddaddy of crypto dies..do you think this grease stain of an ALT with no usage will "MOON" lmao. Glad as hell I got to dump my free ones at 3600 after Conbase got done fookin around.
OMG you really are thick! nobody said btc is dying...old chain is old...slow..expensive...legacy is dying and to make it worse its infected with segwet...something nobody wants. so before infection... btc forked...it upgraded...it evolved... in order to keep up it had too...and look at the result...cheap,fast and soon private tx on-chain. What is it you want? you seem really lost...i feel sorry for you tbh. BCH is BTC It's amazing how biased and censored this forum has become. You are a hero member and the moderator gave you a negative trust because you criticized BTC. Same thing happened to me. BTC has no clothes. Haha couldn't Roger buy this forum ? Don't like it here feel free to join another forum I have joined other forums. I own BTC just like I own other things. Banning me from criticizing BTC is like banning me from criticizing my politician. Moderators are creating echo chambers, which means problems, with the things I own, do not get fixed. r/bitcoin is like the North Korean media, which also likes to ban and censor dissenting viewpoints.
|
|
|
|
|
notthematrix
Legendary
Offline
Activity: 980
Merit: 1000
CryptoTalk.Org - Get Paid for every Post!
|
|
January 12, 2018, 12:34:21 PM |
|
It feels like it's going to go down again, there are no huge news coming and the BTC is ready to go up again, which means BCH will go down
|
|
|
|
amarian12
|
|
January 12, 2018, 12:58:51 PM |
|
i try to upgrade from 16.0.0 to 16.0.3 and get this : 2018-01-12 12:54:14 receive version message: [136.243.139.96:34646] /bitnodes.earn.com:0.1/: version 70015, blocks=512599, us=*.*.*.*, peer=225 2018-01-12 12:54:14 PROCESSMESSAGE: INVALID MESSAGESTART version peer=226 2018-01-12 12:54:15 PROCESSMESSAGE: INVALID MESSAGESTART version peer=227 2018-01-12 12:54:16 PROCESSMESSAGE: INVALID MESSAGESTART version peer=228 2018-01-12 12:54:18 PROCESSMESSAGE: INVALID MESSAGESTART version peer=229 2018-01-12 12:54:18 PROCESSMESSAGE: INVALID MESSAGESTART version peer=230 2018-01-12 12:54:18 PROCESSMESSAGE: INVALID MESSAGESTART version peer=231 2018-01-12 12:54:19 PROCESSMESSAGE: INVALID MESSAGESTART version peer=232 2018-01-12 12:54:20 PROCESSMESSAGE: INVALID MESSAGESTART version peer=233 2018-01-12 12:54:22 PROCESSMESSAGE: INVALID MESSAGESTART version peer=234 2018-01-12 12:54:22 PROCESSMESSAGE: INVALID MESSAGESTART version peer=235 2018-01-12 12:54:23 PROCESSMESSAGE: INVALID MESSAGESTART version peer=236 2018-01-12 12:54:24 PROCESSMESSAGE: INVALID MESSAGESTART version peer=237 2018-01-12 12:54:24 receive version message: [136.243.139.96:35142] /bitnodes.earn.com:0.1/: version 70015, blocks=512599, us=*.*.*.*, peer=238 2018-01-12 12:54:25 PROCESSMESSAGE: INVALID MESSAGESTART version peer=239 2018-01-12 12:54:26 PROCESSMESSAGE: INVALID MESSAGESTART version peer=240 2018-01-12 12:54:26 receive version message: [136.243.139.96:20545] /bitnodes.earn.com:0.1/: version 70015, blocks=512599, us=*.*.*.*, peer=241 2018-01-12 12:54:27 PROCESSMESSAGE: INVALID MESSAGESTART version peer=242 2018-01-12 12:54:27 PROCESSMESSAGE: INVALID MESSAGESTART version peer=243 2018-01-12 12:54:28 PROCESSMESSAGE: INVALID MESSAGESTART version peer=244 2018-01-12 12:54:29 PROCESSMESSAGE: INVALID MESSAGESTART version peer=245 2018-01-12 12:54:31 PROCESSMESSAGE: INVALID MESSAGESTART version peer=246 2018-01-12 12:54:32 PROCESSMESSAGE: INVALID MESSAGESTART version peer=247 2018-01-12 12:54:33 PROCESSMESSAGE: INVALID MESSAGESTART version peer=248 2018-01-12 12:54:34 PROCESSMESSAGE: INVALID MESSAGESTART version peer=249 2018-01-12 12:54:35 PROCESSMESSAGE: INVALID MESSAGESTART version peer=250 2018-01-12 12:54:36 PROCESSMESSAGE: INVALID MESSAGESTART version peer=251 2018-01-12 12:54:36 PROCESSMESSAGE: INVALID MESSAGESTART version peer=252 2018-01-12 12:54:37 PROCESSMESSAGE: INVALID MESSAGESTART version peer=253 2018-01-12 12:54:38 PROCESSMESSAGE: INVALID MESSAGESTART version peer=254 2018-01-12 12:54:39 PROCESSMESSAGE: INVALID MESSAGESTART version peer=255 2018-01-12 12:54:40 PROCESSMESSAGE: INVALID MESSAGESTART version peer=256 2018-01-12 12:54:41 PROCESSMESSAGE: INVALID MESSAGESTART version peer=257 2018-01-12 12:54:42 PROCESSMESSAGE: INVALID MESSAGESTART version peer=258 2018-01-12 12:54:43 PROCESSMESSAGE: INVALID MESSAGESTART version peer=259 2018-01-12 12:54:44 PROCESSMESSAGE: INVALID MESSAGESTART version peer=260 2018-01-12 12:54:45 PROCESSMESSAGE: INVALID MESSAGESTART version peer=261 2018-01-12 12:54:46 PROCESSMESSAGE: INVALID MESSAGESTART version peer=262 2018-01-12 12:54:47 PROCESSMESSAGE: INVALID MESSAGESTART version peer=263 2018-01-12 12:54:48 PROCESSMESSAGE: INVALID MESSAGESTART version peer=264 2018-01-12 12:54:49 PROCESSMESSAGE: INVALID MESSAGESTART version peer=265 2018-01-12 12:54:50 PROCESSMESSAGE: INVALID MESSAGESTART version peer=266 2018-01-12 12:54:51 PROCESSMESSAGE: INVALID MESSAGESTART version peer=267 2018-01-12 12:54:52 PROCESSMESSAGE: INVALID MESSAGESTART version peer=268 2018-01-12 12:54:53 PROCESSMESSAGE: INVALID MESSAGESTART version peer=269 2018-01-12 12:54:54 PROCESSMESSAGE: INVALID MESSAGESTART version peer=270 2018-01-12 12:54:55 PROCESSMESSAGE: INVALID MESSAGESTART version peer=271 2018-01-12 12:54:55 PROCESSMESSAGE: INVALID MESSAGESTART version peer=272 2018-01-12 12:54:56 PROCESSMESSAGE: INVALID MESSAGESTART version peer=273 2018-01-12 12:54:57 PROCESSMESSAGE: INVALID MESSAGESTART version peer=274 2018-01-12 12:54:58 PROCESSMESSAGE: INVALID MESSAGESTART version peer=275 2018-01-12 12:54:59 PROCESSMESSAGE: INVALID MESSAGESTART version peer=276 2018-01-12 12:55:00 PROCESSMESSAGE: INVALID MESSAGESTART version peer=277 2018-01-12 12:55:01 PROCESSMESSAGE: INVALID MESSAGESTART version peer=278 2018-01-12 12:55:01 PROCESSMESSAGE: INVALID MESSAGESTART version peer=279 2018-01-12 12:55:02 PROCESSMESSAGE: INVALID MESSAGESTART version peer=280 2018-01-12 12:55:03 PROCESSMESSAGE: INVALID MESSAGESTART version peer=281 2018-01-12 12:55:04 PROCESSMESSAGE: INVALID MESSAGESTART version peer=282 2018-01-12 12:55:05 PROCESSMESSAGE: INVALID MESSAGESTART version peer=283 2018-01-12 12:55:06 PROCESSMESSAGE: INVALID MESSAGESTART version peer=284 2018-01-12 12:55:07 PROCESSMESSAGE: INVALID MESSAGESTART version peer=285 2018-01-12 12:55:08 PROCESSMESSAGE: INVALID MESSAGESTART version peer=286 2018-01-12 12:55:09 PROCESSMESSAGE: INVALID MESSAGESTART version peer=287 2018-01-12 12:55:11 PROCESSMESSAGE: INVALID MESSAGESTART version peer=288 2018-01-12 12:55:12 PROCESSMESSAGE: INVALID MESSAGESTART version peer=289 2018-01-12 12:55:13 PROCESSMESSAGE: INVALID MESSAGESTART version peer=290 2018-01-12 12:55:13 PROCESSMESSAGE: INVALID MESSAGESTART version peer=291 2018-01-12 12:55:14 PROCESSMESSAGE: INVALID MESSAGESTART version peer=292 2018-01-12 12:55:14 PROCESSMESSAGE: INVALID MESSAGESTART version peer=293 2018-01-12 12:55:16 PROCESSMESSAGE: INVALID MESSAGESTART version peer=294 2018-01-12 12:55:16 PROCESSMESSAGE: INVALID MESSAGESTART version peer=295 2018-01-12 12:55:17 PROCESSMESSAGE: INVALID MESSAGESTART version peer=296 2018-01-12 12:55:18 PROCESSMESSAGE: INVALID MESSAGESTART version peer=297 2018-01-12 12:55:19 PROCESSMESSAGE: INVALID MESSAGESTART version peer=298 2018-01-12 12:55:20 PROCESSMESSAGE: INVALID MESSAGESTART version peer=299 2018-01-12 12:55:21 PROCESSMESSAGE: INVALID MESSAGESTART version peer=300 2018-01-12 12:55:22 PROCESSMESSAGE: INVALID MESSAGESTART version peer=301 2018-01-12 12:55:23 PROCESSMESSAGE: INVALID MESSAGESTART version peer=302 2018-01-12 12:55:24 PROCESSMESSAGE: INVALID MESSAGESTART version peer=303 2018-01-12 12:55:25 PROCESSMESSAGE: INVALID MESSAGESTART version peer=304 2018-01-12 12:55:27 PROCESSMESSAGE: INVALID MESSAGESTART version peer=305 2018-01-12 12:55:28 PROCESSMESSAGE: INVALID MESSAGESTART version peer=306 2018-01-12 12:55:29 PROCESSMESSAGE: INVALID MESSAGESTART version peer=307 2018-01-12 12:55:30 PROCESSMESSAGE: INVALID MESSAGESTART version peer=308 2018-01-12 12:55:31 PROCESSMESSAGE: INVALID MESSAGESTART version peer=309 2018-01-12 12:55:32 PROCESSMESSAGE: INVALID MESSAGESTART version peer=310 2018-01-12 12:55:33 PROCESSMESSAGE: INVALID MESSAGESTART version peer=311 2018-01-12 12:55:34 PROCESSMESSAGE: INVALID MESSAGESTART version peer=312 2018-01-12 12:55:35 PROCESSMESSAGE: INVALID MESSAGESTART version peer=313 2018-01-12 12:55:36 PROCESSMESSAGE: INVALID MESSAGESTART version peer=314 2018-01-12 12:55:37 PROCESSMESSAGE: INVALID MESSAGESTART version peer=315 2018-01-12 12:55:37 PROCESSMESSAGE: INVALID MESSAGESTART version peer=316 2018-01-12 12:55:38 PROCESSMESSAGE: INVALID MESSAGESTART version peer=317 2018-01-12 12:55:39 PROCESSMESSAGE: INVALID MESSAGESTART version peer=318 2018-01-12 12:55:39 PROCESSMESSAGE: INVALID MESSAGESTART version peer=319 2018-01-12 12:55:40 PROCESSMESSAGE: INVALID MESSAGESTART version peer=320 2018-01-12 12:55:41 PROCESSMESSAGE: INVALID MESSAGESTART version peer=321 2018-01-12 12:55:42 PROCESSMESSAGE: INVALID MESSAGESTART version peer=322 2018-01-12 12:55:44 PROCESSMESSAGE: INVALID MESSAGESTART version peer=323 2018-01-12 12:55:45 PROCESSMESSAGE: INVALID MESSAGESTART version peer=324 2018-01-12 12:55:46 PROCESSMESSAGE: INVALID MESSAGESTART version peer=325 2018-01-12 12:55:46 receive version message: [5.189.177.233:21124] /bitnodes.bitcoinunlimited.info:0.1/: version 70015, blocks=512599, us=*.*.*.*, peer=326 2018-01-12 12:55:47 PROCESSMESSAGE: INVALID MESSAGESTART version peer=327 2018-01-12 12:55:48 PROCESSMESSAGE: INVALID MESSAGESTART version peer=328 2018-01-12 12:55:49 PROCESSMESSAGE: INVALID MESSAGESTART version peer=329 2018-01-12 12:55:49 receive version message: [5.189.177.233:57845] /bitnodes.bitcoinunlimited.info:0.1/: version 70015, blocks=512599, us=*.*.*.*, peer=330 2018-01-12 12:55:50 PROCESSMESSAGE: INVALID MESSAGESTART version peer=331 2018-01-12 12:55:51 PROCESSMESSAGE: INVALID MESSAGESTART version peer=332 2018-01-12 12:55:52 PROCESSMESSAGE: INVALID MESSAGESTART version peer=333 2018-01-12 12:55:53 PROCESSMESSAGE: INVALID MESSAGESTART version peer=334 2018-01-12 12:55:54 PROCESSMESSAGE: INVALID MESSAGESTART version peer=335 2018-01-12 12:55:55 PROCESSMESSAGE: INVALID MESSAGESTART version peer=336 2018-01-12 12:55:56 PROCESSMESSAGE: INVALID MESSAGESTART version peer=337 2018-01-12 12:55:56 PROCESSMESSAGE: INVALID MESSAGESTART version peer=338 2018-01-12 12:55:57 PROCESSMESSAGE: INVALID MESSAGESTART version peer=339 2018-01-12 12:55:59 PROCESSMESSAGE: INVALID MESSAGESTART version peer=340 2018-01-12 12:55:59 PROCESSMESSAGE: INVALID MESSAGESTART version peer=341 2018-01-12 12:56:00 PROCESSMESSAGE: INVALID MESSAGESTART version peer=342 2018-01-12 12:56:01 PROCESSMESSAGE: INVALID MESSAGESTART version peer=343 2018-01-12 12:56:02 connect() to 112.207.57.182:8333 failed after select(): Connection refused (111) 2018-01-12 12:56:02 PROCESSMESSAGE: INVALID MESSAGESTART version peer=344 2018-01-12 12:56:03 PROCESSMESSAGE: INVALID MESSAGESTART version peer=345 2018-01-12 12:56:04 PROCESSMESSAGE: INVALID MESSAGESTART version peer=346 2018-01-12 12:56:05 PROCESSMESSAGE: INVALID MESSAGESTART version peer=347 2018-01-12 12:56:06 PROCESSMESSAGE: INVALID MESSAGESTART version peer=348 2018-01-12 12:56:07 PROCESSMESSAGE: INVALID MESSAGESTART version peer=349 2018-01-12 12:56:08 PROCESSMESSAGE: INVALID MESSAGESTART version peer=350 2018-01-12 12:56:09 PROCESSMESSAGE: INVALID MESSAGESTART version peer=351 2018-01-12 12:56:10 PROCESSMESSAGE: INVALID MESSAGESTART version peer=352
|
Imagine a future where IT infrastructures monitor themselves, are able to predict and respond to future business needs and can protect and heal themselves automatically.
|
|
|
|