Just recall I have one share of NEM, dumped all of them and got more than two million Yuan, this is fantastic! All of these money are free with no effort!  wow lucky to still have the keys |
|
|
|
|
To the top 3 now!!!! Lets GOOOOOOO!
|
|
|
|
Avalon Life Puts Land Ownership on Blockchain, Launches GREEN EARTH ZERO Service with NEM Technology
Bitcoin Press Release: Avalon Life announces Green Earth Zero tokens, makes buying less than one square meter of land possible in Costa Rica.
May 15, 2017, San Jose, Costa Rica – Avalon Life, a cryptocurrency mining company has announced the launch of an innovative GREEN EARTH ZERO service, backed by the namesake Green Earth Zero token. Created using the NEM blockchain technology, GREEN EARTH ZERO service enables participants to own land by the square meter in Costa Rica.
Avalon Life has incorporated a simple, easy to use three step process for the users to sign up and buy Green Earth Zero tokens directly on the blockchain platform in a quick and secure way. Avalon Life has developed a customized blockchain wallet based on NEM technology to release this service.
Source: http://bitcoinprbuzz.com/press-release-avalon-life/ no price spike with this "news"....  other coins get a good bump on any news  |
|
|
|
Yes,this online wallets are very easy to use,and can easily add custom token. so i just send edg to the eth address? yes sir..... thanks  |
|
|
|
Yes,this online wallets are very easy to use,and can easily add custom token. so i just send edg to the eth address? |
|
|
|
|
what are the details on the ipo? min/max? escrow? cant find any info on the site
|
|
|
|
|
any wallet for edge? how do you store the coins?
|
|
|
|
|
ripple almost 10 bil!!!, i feel its gonna dump hard soon
|
|
|
|
|
ONLY 250,000,000$ increase required in market cap to be number 4!!!
|
|
|
|
CoinDash's Social Bounty Campaign The duration of the campaign will be from its starting day expected to be on July 2017, until the end of its ICO weather by its finishing date or by reaching its full cap. so this is not open now??? |
|
|
|
Is it possible to have supernode and use delegate harvesting at the same time on one wallet?
Good question A supernode is just a node with minimum requirement. It has nothing to do with a wallet. You can of course harvest with the delegated account that the supernode is using. Xem Nem 2017/2018 1/10$ I pray for this 10$ is pretty impossible even in 2020......i wish it happens though  |
|
|
|
the link says its less safe to use someone elses node, so ill prefer running my own node. there is no error, its just stuck
Have you tried closing the GUI, waiting 20 seconds, then restarting the GUI? As for using a remote node, the risks are minimal. You may not be ok with this though...I'm just presenting an option. Here's more info on the risks: https://www.reddit.com/r/Monero/comments/5myxam/remote_nodes_to_use_or_not_to_use/If you start and restart the GUI and it still gets stuck, please post back. the blocks remaining have actually increased to 948346! is there anyway to import the blockchain file? this is the daemon error i get: 2017-05-10 22:14:56.117 13320 INFO global contrib/epee/src/mlog.cpp:145 New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO
2017-05-10 22:14:57.147 13320 ERROR msgwriter src/common/scoped_message_writer.h:94 Error: Couldn't connect to daemon
Error: Couldn't connect to daemon
2017-05-10 22:15:05.079 10188 INFO global contrib/epee/src/mlog.cpp:145 New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO
2017-05-10 22:15:06.084 10188 ERROR msgwriter src/common/scoped_message_writer.h:94 Error: Couldn't connect to daemon
Error: Couldn't connect to daemon
2017-05-10 22:15:08.170 9560 INFO global contrib/epee/src/mlog.cpp:145 New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO
2017-05-10 22:15:09.183 9560 ERROR msgwriter src/common/scoped_message_writer.h:94 Error: Couldn't connect to daemon
Error: Couldn't connect to daemon
2017-05-10 22:15:11.307 352 INFO global contrib/epee/src/mlog.cpp:145 New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO
Height: 358852/358852 (100.0%) on mainnet, not mining, net hash 14.45 MH/s, v1, up to date, 0(out)+0(in) connections, uptime 0d 0h 0m 3s
2017-05-11 00:21:40.601 12332 INFO global contrib/epee/src/mlog.cpp:145 New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO
Height: 358852/1307198 (27.5%) on mainnet, not mining, net hash 14.45 MH/s, v1, up to date, 4(out)+0(in) connections, uptime 0d 2h 6m 30s
2017-05-11 00:23:11.339 10924 INFO global contrib/epee/src/mlog.cpp:145 New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO
Stop signal sent
2017-05-11 00:23:13.515 9432 INFO global contrib/epee/src/mlog.cpp:145 New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO
Height: 358852/1307198 (27.5%) on mainnet, not mining, net hash 14.45 MH/s, v1, up to date, 4(out)+0(in) connections, uptime 0d 2h 8m 3s
2017-05-11 00:23:15.689 12836 INFO global contrib/epee/src/mlog.cpp:145 New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO
Height: 358852/1307198 (27.5%) on mainnet, not mining, net hash 14.45 MH/s, v1, up to date, 4(out)+0(in) connections, uptime 0d 2h 8m 5s
2017-05-11 00:23:17.859 10368 INFO global contrib/epee/src/mlog.cpp:145 New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO
Height: 358852/1307198 (27.5%) on mainnet, not mining, net hash 14.45 MH/s, v1, up to date, 4(out)+0(in) connections, uptime 0d 2h 8m 7s
2017-05-11 00:23:20.059 14064 INFO global contrib/epee/src/mlog.cpp:145 New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO
Height: 358852/1307198 (27.5%) on mainnet, not mining, net hash 14.45 MH/s, v1, up to date, 4(out)+0(in) connections, uptime 0d 2h 8m 10s
2017-05-11 00:23:22.254 12356 INFO global contrib/epee/src/mlog.cpp:145 New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO
Height: 358852/1307198 (27.5%) on mainnet, not mining, net hash 14.45 MH/s, v1, up to date, 4(out)+0(in) connections, uptime 0d 2h 8m 12s
2017-05-11 00:23:26.111 12324 INFO global contrib/epee/src/mlog.cpp:145 New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO
2017-05-11 00:23:27.155 12324 ERROR msgwriter src/common/scoped_message_writer.h:94 Error: Couldn't connect to daemon
Error: Couldn't connect to daemon
2017-05-11 00:24:35.709 14696 INFO global contrib/epee/src/mlog.cpp:145 New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO
2017-05-11 00:24:36.723 14696 ERROR msgwriter src/common/scoped_message_writer.h:94 Error: Couldn't connect to daemon
Error: Couldn't connect to daemon
2017-05-11 00:24:38.863 14200 INFO global contrib/epee/src/mlog.cpp:145 New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO
2017-05-11 00:24:39.876 14200 ERROR msgwriter src/common/scoped_message_writer.h:94 Error: Couldn't connect to daemon
Error: Couldn't connect to daemon
2017-05-11 00:24:42.098 3572 INFO global contrib/epee/src/mlog.cpp:145 New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO
Height: 358852/358852 (100.0%) on mainnet, not mining, net hash 14.45 MH/s, v1, up to date, 0(out)+0(in) connections, uptime 0d 0h 0m 3s
2017-05-11 00:25:26.109 2136 INFO global contrib/epee/src/mlog.cpp:145 New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO
Stop signal sent
2017-05-11 00:25:28.308 14800 INFO global contrib/epee/src/mlog.cpp:145 New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO
Height: 358852/1307246 (27.5%) on mainnet, not mining, net hash 14.45 MH/s, v1, up to date, 7(out)+0(in) connections, uptime 0d 0h 0m 47s
2017-05-11 00:25:30.484 13808 INFO global contrib/epee/src/mlog.cpp:145 New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO
Height: 358852/1307246 (27.5%) on mainnet, not mining, net hash 14.45 MH/s, v1, up to date, 7(out)+0(in) connections, uptime 0d 0h 0m 49s
2017-05-11 00:25:32.651 6544 INFO global contrib/epee/src/mlog.cpp:145 New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO
Height: 358852/1307246 (27.5%) on mainnet, not mining, net hash 14.45 MH/s, v1, up to date, 7(out)+0(in) connections, uptime 0d 0h 0m 51s
2017-05-11 00:25:34.852 9448 INFO global contrib/epee/src/mlog.cpp:145 New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO
Height: 358852/1307246 (27.5%) on mainnet, not mining, net hash 14.45 MH/s, v1, up to date, 7(out)+0(in) connections, uptime 0d 0h 0m 53s
2017-05-11 00:25:37.115 3200 INFO global contrib/epee/src/mlog.cpp:145 New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO
Height: 358852/1307246 (27.5%) on mainnet, not mining, net hash 14.45 MH/s, v1, up to date, 7(out)+0(in) connections, uptime 0d 0h 0m 56s
2017-05-11 00:25:40.210 4088 INFO global contrib/epee/src/mlog.cpp:145 New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO
2017-05-11 00:25:41.469 4088 ERROR msgwriter src/common/scoped_message_writer.h:94 Error: Couldn't connect to daemon
Error: Couldn't connect to daemon
2017-05-11 00:26:10.938 13692 INFO global contrib/epee/src/mlog.cpp:145 New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO
2017-05-11 00:26:11.943 13692 ERROR msgwriter src/common/scoped_message_writer.h:94 Error: Couldn't connect to daemon
Error: Couldn't connect to daemon
|
|
|
|
why are we suddenly performing the worst Assuming this recent rise didn't happen, this would just be a gradual rise. The bigger picture is still good. yes its much better than rising 300-400% in a couple days like stellar.....goes underground during the dump lol.....xem will not lose value quickly because of the steady rise... |
|
|
|
the link says its less safe to use someone elses node, so ill prefer running my own node. there is no error, its just stuck
Have you tried closing the GUI, waiting 20 seconds, then restarting the GUI? As for using a remote node, the risks are minimal. You may not be ok with this though...I'm just presenting an option. Here's more info on the risks: https://www.reddit.com/r/Monero/comments/5myxam/remote_nodes_to_use_or_not_to_use/If you start and restart the GUI and it still gets stuck, please post back. the blocks remaining have actually increased to 948346! is there anyway to import the blockchain file? |
|
|
|
It went up 30x in the space of a few weeks. If you weren't expecting a vast crash, and this isn't it yet, then expect some sadness in the future.
30x  its like 6x rise in about 10 weeks....see the charts |
|
|
|
why are we suddenly performing the worst |
|
|
|
|
Show Posts
