Topic: Vereum ICO - Vereum - EOS - Ethereum Vereum Jelly Network Blockchain - page 4. (Read 2111 times)

Hello Margary,

For country restrictions, please refer to our Terms of Use & Terms of Sale which is located on our website vereum.io

Best wishes,

Team Vereum.

Hey guys,

Everything is resolved regarding the attack - just to let you know, that when mining Vereum it requires (like BTC) good mining power and in Gigahash.

If you have any questions don't hesitate to email us at [email protected]

Best wishes,

Team Vereum.

It went back to normal. It is like jumping going off and on and going very slow overall. Probably due to the attack

Block 376 problem, dev please check help me.

Now it got stuck at 376. What is wrong with this blockchain? 

Hi!

I have bought few VMC from https://vereum.io/
However in my account it shows as VRM. Is VMC and VRM are same?

By using vereum, you can create a contract that will hold a contributor's money until any given date or goal is reached. Depending on the outcome, the funds will either be released to the project owners or safely returned back to the contributors. All of this is possible without requiring a centralized arbitrator, clearinghouse or having to trust anyone. You can even use the coin you created earlier to keep track of the distribution of rewards.

Since the project is good, mining for this coins should be interesting too. and taking many profit should be easy.
merculet

Great project with a great team and supporters. Who are the teams in this project ?

1Ghash! oops. 

block 308 was stuck. difg block 4xx. it should be change to the next block for 1 hours for 1GH hash. Vereum team should be check the server chain. its impossible to mine / doing masternode if the block never change.

I am afraid I cannot be of any help. I have barely a couple of mhs. So what is the solution? I have to mine that block for one year?? Or just wait for the next wallet release, probably.

Thank you but my wallet is still not syncing. I tried all the typical stuff of deleting everything except the .conf and wallet.dat files and restarting, but nothing is working. I also tried three different computers and in node of them could it sync. It's still showing 5 days behind.

Here is my debug.log. Here I notice that the time is set two hours earlier than my actual time. Time on the computer is nevertheless set correctly and in the wallet's debug window time is also shown correctly. with 'getinfo' I get 'timeoffset=0', which is good. Any ideas?:

2018-04-27 22:33:03 Vereum version v1.0.0.0 ()
2018-04-27 22:33:03 Using OpenSSL version OpenSSL 1.0.2g  1 Mar 2016
2018-04-27 22:33:03 Default data directory /root/.vereum
2018-04-27 22:33:03 Using data directory /root/.vereum
2018-04-27 22:33:03 Using at most 125 connections (1024 file descriptors available)
2018-04-27 22:33:03 Using 8 threads for script verification
2018-04-27 22:33:03 init message: Verifying wallet...
2018-04-27 22:33:03 dbenv.open LogDir=/root/.vereum/database ErrorFile=/root/.vereum/db.log
2018-04-27 22:33:03 Bound to [::]:36349
2018-04-27 22:33:03 Bound to 0.0.0.0:36349
2018-04-27 22:33:03 init message: Loading block index...
2018-04-27 22:33:03 Opening LevelDB in /root/.vereum/blocks/index
2018-04-27 22:33:03 Opened LevelDB successfully
2018-04-27 22:33:03 Opening LevelDB in /root/.vereum/chainstate
2018-04-27 22:33:03 Opened LevelDB successfully
2018-04-27 22:33:03 LoadBlockIndexDB(): last block file = 0
2018-04-27 22:33:03 LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=309, size=141436, heights=0...308, time=2018-04-11...2018-04-22)
2018-04-27 22:33:03 LoadBlockIndexDB(): transaction index disabled
2018-04-27 22:33:03 LoadBlockIndexDB(): hashBestChain=0b2f68af4cf836f357f146dca4185795f606f6ae072a39dc71d640084df07533  height=308 date=2018-04-22 16:52:53
2018-04-27 22:33:03 init message: Verifying blocks...
2018-04-27 22:33:03 Verifying last 288 blocks at level 3
2018-04-27 22:33:03 No coin database inconsistencies in last 289 blocks (430 transactions)
2018-04-27 22:33:03  block index             914ms
2018-04-27 22:33:03 init message: Loading wallet...
2018-04-27 22:33:04 nFileVersion = 1000000
2018-04-27 22:33:04  wallet                  397ms
2018-04-27 22:33:04 init message: Loading addresses...
2018-04-27 22:33:04 Loaded 27 addresses from peers.dat  0ms
2018-04-27 22:33:04 mapBlockIndex.size() = 309
2018-04-27 22:33:04 nBestHeight = 308
2018-04-27 22:33:04 setKeyPool.size() = 102
2018-04-27 22:33:04 mapWallet.size() = 120
2018-04-27 22:33:04 mapAddressBook.size() = 1
2018-04-27 22:33:04 opencon thread start
2018-04-27 22:33:04 init message: Done loading
2018-04-27 22:33:04 net thread start
2018-04-27 22:33:04 upnp thread start
2018-04-27 22:33:04 dnsseed thread start
2018-04-27 22:33:04 Loading addresses from DNS seeds (could take a while)
2018-04-27 22:33:04 2 addresses found from DNS seeds
2018-04-27 22:33:04 dnsseed thread exit
2018-04-27 22:33:04 dumpaddr thread start
2018-04-27 22:33:04 addcon thread start
2018-04-27 22:33:04 trying connection 37.97.242.80:36349 lastseen=395796,8hrs
2018-04-27 22:33:04 msghand thread start
2018-04-27 22:33:04 connected 37.97.242.80:36349
2018-04-27 22:33:04 send version message: version 70002, blocks=308, us=0.0.0.0:0, them=37.97.242.80:36349, peer=37.97.242.80:36349
2018-04-27 22:33:04 GetMyExternalIP() received [87.218.159.61] 87.218.159.61:0
2018-04-27 22:33:04 GetMyExternalIP() returned 87.218.159.61
2018-04-27 22:33:04 AddLocal(87.218.159.61:36349,4)
2018-04-27 22:33:04 UPnP: ExternalIPAddress = 0.0.0.0
2018-04-27 22:33:04 Added time data, samples 2, offset -7 (+0 minutes)
2018-04-27 22:33:04 receive version message: /Satoshi:1.0.0/: version 70002, blocks=308, us=87.218.159.61:51500, them=37.97.242.80:36349, peer=37.97.242.80:36349
2018-04-27 22:33:04 trying connection 61.164.253.37:36349 lastseen=0,0hrs
2018-04-27 22:33:04 trying connection 159.65.160.80:36349 lastseen=395796,8hrs
2018-04-27 22:33:05 UPnP Port Mapping successful.
2018-04-27 22:33:05 connected 159.65.160.80:36349
2018-04-27 22:33:05 send version message: version 70002, blocks=308, us=87.218.159.61:36349, them=159.65.160.80:36349, peer=159.65.160.80:36349
2018-04-27 22:33:05 connected 61.164.253.37:36349
2018-04-27 22:33:05 send version message: version 70002, blocks=308, us=87.218.159.61:36349, them=61.164.253.37:36349, peer=61.164.253.37:36349
2018-04-27 22:33:05 refreshWallet
2018-04-27 22:33:05 Added time data, samples 3, offset +0 (+0 minutes)
2018-04-27 22:33:05 receive version message: /Satoshi:1.0.0/: version 70002, blocks=308, us=87.218.159.61:38688, them=159.65.160.80:36349, peer=159.65.160.80:36349
2018-04-27 22:33:05 Added time data, samples 4, offset +0 (+0 minutes)
2018-04-27 22:33:05 receive version message: /Satoshi:1.0.0/: version 70002, blocks=308, us=87.218.159.61:38316, them=61.164.253.37:36349, peer=61.164.253.37:36349
2018-04-27 22:33:05 trying connection 5.9.0.216:36349 lastseen=395796,8hrs
2018-04-27 22:33:05 trying connection 77.35.18.13:36349 lastseen=0,0hrs
2018-04-27 22:33:05 connected 5.9.0.216:36349
2018-04-27 22:33:05 send version message: version 70002, blocks=308, us=87.218.159.61:36349, them=5.9.0.216:36349, peer=5.9.0.216:36349
2018-04-27 22:33:05 Added time data, samples 5, offset +0 (+0 minutes)
2018-04-27 22:33:05 nTimeOffset = +0  (+0 minutes)
2018-04-27 22:33:05 receive version message: /Satoshi:1.0.0/: version 70002, blocks=308, us=87.218.159.61:53502, them=5.9.0.216:36349, peer=5.9.0.216:36349
2018-04-27 22:33:06 connected 77.35.18.13:36349
2018-04-27 22:33:06 send version message: version 70002, blocks=308, us=87.218.159.61:36349, them=77.35.18.13:36349, peer=77.35.18.13:36349
2018-04-27 22:33:06 trying connection 206.189.18.241:36349 lastseen=395796,8hrs
2018-04-27 22:33:06 connected 206.189.18.241:36349
2018-04-27 22:33:06 send version message: version 70002, blocks=308, us=87.218.159.61:36349, them=206.189.18.241:36349, peer=206.189.18.241:36349
2018-04-27 22:33:06 trying connection 217.182.166.152:36349 lastseen=115,7hrs
2018-04-27 22:33:06 Added time data, samples 6, offset +240 (+4 minutes)
2018-04-27 22:33:06 receive version message: /Satoshi:1.0.0/: version 70002, blocks=308, us=87.218.159.61:52650, them=77.35.18.13:36349, peer=77.35.18.13:36349
2018-04-27 22:33:06 Added time data, samples 7, offset +0 (+0 minutes)
2018-04-27 22:33:06 nTimeOffset = +0  (+0 minutes)
2018-04-27 22:33:06 receive version message: /Satoshi:1.0.0/: version 70002, blocks=308, us=87.218.159.61:44020, them=206.189.18.241:36349, peer=206.189.18.241:36349
2018-04-27 22:33:06 connect() failed after select(): Connection refused
2018-04-27 22:33:06 Added 1 addresses from 5.9.0.216: 7 tried, 21 new
2018-04-27 22:33:06 trying connection 138.68.100.178:36349 lastseen=395796,8hrs
2018-04-27 22:33:06 connected 138.68.100.178:36349
2018-04-27 22:33:06 send version message: version 70002, blocks=308, us=87.218.159.61:36349, them=138.68.100.178:36349, peer=138.68.100.178:36349
2018-04-27 22:33:06 Added 1 addresses from 37.97.242.80: 7 tried, 22 new
2018-04-27 22:33:07 trying connection 212.225.240.167:36349 lastseen=2,4hrs
2018-04-27 22:33:07 Added time data, samples 8, offset +0 (+0 minutes)
2018-04-27 22:33:07 Moving 138.68.100.178:36349 to tried
2018-04-27 22:33:07 receive version message: /Satoshi:1.0.0/: version 70002, blocks=308, us=87.218.159.61:47168, them=138.68.100.178:36349, peer=138.68.100.178:36349
2018-04-27 22:33:07 Added 1 addresses from 159.65.160.80: 8 tried, 22 new
2018-04-27 22:33:07 Added 1 addresses from 138.68.100.178: 8 tried, 23 new
2018-04-27 22:33:08 Added 1 addresses from 61.164.253.37: 8 tried, 24 new
2018-04-27 22:33:12 connection timeout
2018-04-27 22:33:12 trying connection 77.66.200.240:36349 lastseen=395796,8hrs
2018-04-27 22:33:17 connection timeout
2018-04-27 22:33:20 trying connection 212.225.240.167:36349 lastseen=2,5hrs
2018-04-27 22:33:25 connection timeout
2018-04-27 22:33:25 trying connection 2.222.83.52:36349 lastseen=167,9hrs
2018-04-27 22:33:30 connection timeout
2018-04-27 22:33:31 trying connection 5.189.171.146:36349 lastseen=99,2hrs
2018-04-27 22:33:36 connection timeout
2018-04-27 22:33:37 trying connection 90.201.119.97:36349 lastseen=123,6hrs
2018-04-27 22:33:42 connection timeout
2018-04-27 22:33:42 trying connection 212.225.240.167:36349 lastseen=2,5hrs
2018-04-27 22:33:47 connection timeout
2018-04-27 22:33:48 trying connection 5.143.99.153:36349 lastseen=40,1hrs
2018-04-27 22:33:53 connection timeout
2018-04-27 22:33:53 trying connection 175.145.244.65:36349 lastseen=167,0hrs
2018-04-27 22:33:58 connection timeout
2018-04-27 22:33:59 trying connection 212.225.240.167:36349 lastseen=2,5hrs
2018-04-27 22:34:04 connection timeout
2018-04-27 22:34:04 trying connection 191.252.103.206:36349 lastseen=0,1hrs
2018-04-27 22:34:04 connected 191.252.103.206:36349
2018-04-27 22:34:04 send version message: version 70002, blocks=308, us=87.218.159.61:36349, them=191.252.103.206:36349, peer=191.252.103.206:36349
2018-04-27 22:34:05 Added time data, samples 9, offset +0 (+0 minutes)
2018-04-27 22:34:05 nTimeOffset = +0  (+0 minutes)
2018-04-27 22:34:05 receive version message: /Satoshi:1.0.0/: version 70002, blocks=308, us=87.218.159.61:49190, them=191.252.103.206:36349, peer=191.252.103.206:36349
2018-04-27 22:39:36 keypool reserve 17
2018-04-27 22:39:36 keypool return 17
2018-04-27 22:46:50 ResendWalletTransactions()
2018-04-27 22:48:04 Flushed 32 addresses to peers.dat  46ms

What are the nodes for this coin? My wallet is not syncing.

Hey guys,

The Vereum team are pleased to announce that the technical paper is now live!

Check it out at: https://vereum.io/vereum-tech-paper_V1.2.pdf

If you have any specific questions about vereum don't hesitate to contact us at [email protected]

Pre-Sale launches on May 1st 2018!

Team Vereum.

I'm curious about whethe,r there are restrictions on investing for people from some countries? can all people invest their money in this project to get the internal tokens of this project, are there primary restrictions in the regions?

Hello guys!

Big update from the Vereum team. We have been developing vereum.io and nearly ready to re-launch the pre-sale.

We are proud to issue you with our brand new whitepaper, which details the Vereum project and how to get involved.

Read about the Revolution of Cryptocurrency - https://vereum.io/Vereum-Whitepaper_V3.3.pdf

Technical Whitepaper coming soon.

Team Vereum.

this coin really price 0.05 satohi
when varius coin started coinexchange.io
?

 have been added to coinexchange.io




https://www.coinexchange.io/market/VMC/BTC