Topic: [$XVG] VERGE [POW][MultiAlgo][TOR/i2P][no premine/ico!] - page 516. (Read 843765 times)

Quote from: VDechand on April 12, 2016, 11:15:40 AM

I think I fixed the wallet mining, the diff reporting and the broken algos.
There are at least two bugs.
Unfortunately I can't test the block generation because the network is refusing my x17 blocks.

EDIT: do you want me to submit a pull request with the fixes?

EDIT2: a hard fork is necessary to fix x17 and blake2s; they won't work unless most wallets are upgraded.

ok. so that one character change is what was holding back x17 and blake2s? interesting. well, include the fork at 350,000, and i will merge it later today.

So does this mean another wallet and update of all the blocks at 350K again with eveyone and the exchanges?

Just a new wallet, no need to resync.

DeadBirdzz

sr. member

Activity: 336

Merit: 252

I have a question. I send XVG coins to the yobit wallet, after 4 hours the coins aren´t in the yobit wallet. Is this a mistake from yobit? The support can´t solve my question

Quote from: amirmass on April 12, 2016, 10:50:16 AM

why XVG deposites to yobit are taking more than 1 day?? this is insane , anyone have the same problem?

Okay i see it, i´m not alone ^^

Yobit's Wallet status: Online (340013 blocks)

They haven't synced yet......

VDechand

sr. member

Activity: 358

Merit: 250

I have a question. I send XVG coins to the yobit wallet, after 4 hours the coins aren´t in the yobit wallet. Is this a mistake from yobit? The support can´t solve my question

Quote from: amirmass on April 12, 2016, 10:50:16 AM

why XVG deposites to yobit are taking more than 1 day?? this is insane , anyone have the same problem?

Okay i see it, i´m not alone ^^

g0ldm0ney10

full member

Activity: 146

Merit: 100

Quote from: Dogedarkdev on April 12, 2016, 08:57:13 AM

Quote from: pallas on April 12, 2016, 09:03:16 AM

I think I fixed the wallet mining, the diff reporting and the broken algos.
There are at least two bugs.
Unfortunately I can't test the block generation because the network is refusing my x17 blocks.

EDIT: do you want me to submit a pull request with the fixes?

EDIT2: a hard fork is necessary to fix x17 and blake2s; they won't work unless most wallets are upgraded.

ok. so that one character change is what was holding back x17 and blake2s? interesting. well, include the fork at 350,000, and i will merge it later today.

So does this mean another wallet and update of all the blocks at 350K again with eveyone and the exchanges?

amirmass

sr. member

Activity: 425

Merit: 250

why XVG deposites to yobit are taking more than 1 day?? this is insane , anyone have the same problem?

Dogedarkdev

legendary

Activity: 1708

Merit: 1009

$XVG - The Standard in Crypto as a Currency!

Quote from: Dogedarkdev on April 12, 2016, 08:57:13 AM

Quote from: Dogedarkdev on April 12, 2016, 08:57:13 AM

I think I fixed the wallet mining, the diff reporting and the broken algos.
There are at least two bugs.
Unfortunately I can't test the block generation because the network is refusing my x17 blocks.

EDIT: do you want me to submit a pull request with the fixes?

EDIT2: a hard fork is necessary to fix x17 and blake2s; they won't work unless most wallets are upgraded.

ok. so that one character change is what was holding back x17 and blake2s? interesting. well, include the fork at 350,000, and i will merge it later today.

yes because the algo is taken from the version field of the blockheader: if the mask is wrong, some algos are mapped to the default, which is scrypt, hence the hash mismatch.
in this case, groestl and lyra were not affected because their bits felt under the old wrong mask.
not sure if you are asking me to "include the fork at 350,000" or if you or someone else's gonna do it.

yeah i meant you can add it to the pr you made. i wrote you back on the repo. thanks for the contribution!

pallas

legendary

Activity: 2716

Merit: 1094

Black Belt Developer

I think I fixed the wallet mining, the diff reporting and the broken algos.
There are at least two bugs.
Unfortunately I can't test the block generation because the network is refusing my x17 blocks.

EDIT: do you want me to submit a pull request with the fixes?

EDIT2: a hard fork is necessary to fix x17 and blake2s; they won't work unless most wallets are upgraded.

ok. so that one character change is what was holding back x17 and blake2s? interesting. well, include the fork at 350,000, and i will merge it later today.

yes because the algo is taken from the version field of the blockheader: if the mask is wrong, some algos are mapped to the default, which is scrypt, hence the hash mismatch.
in this case, groestl and lyra were not affected because their bits felt under the old wrong mask.
not sure if you are asking me to "include the fork at 350,000" or if you or someone else's gonna do it.

Dogedarkdev

legendary

Activity: 1708

Merit: 1009

$XVG - The Standard in Crypto as a Currency!

Quote from: Dogedarkdev on April 12, 2016, 05:44:45 AM

I think I fixed the wallet mining, the diff reporting and the broken algos.
There are at least two bugs.
Unfortunately I can't test the block generation because the network is refusing my x17 blocks.

EDIT: do you want me to submit a pull request with the fixes?

EDIT2: a hard fork is necessary to fix x17 and blake2s; they won't work unless most wallets are upgraded.

ok. so that one character change is what was holding back x17 and blake2s? interesting. well, include the fork at 350,000, and i will merge it later today.

p75formula

hero member

Activity: 533

Merit: 500

Bleu under maintenance so they're working on it. Roll Eyes

Way to keep up boys.

bitLeap

sr. member

Activity: 1204

Merit: 486

ps: cryptsy is not in control of their funds anymore,

that's what matters

crysx

sr. member

Activity: 364

Merit: 260

--- ChainWorks Industries ---

Quote from: pallas on April 12, 2016, 06:59:32 AM

Quote from: crysx on April 12, 2016, 06:58:34 AM

Quote from: pallas on April 12, 2016, 04:48:43 AM

Quote from: Dogedarkdev on April 11, 2016, 10:38:13 PM

Quote from: Dogedarkdev on April 12, 2016, 05:44:45 AM

hi all ...

after compiling from the git ( yesterday ) - the wallet STILL says 'warning: this version is obsolete, upgrade required' ...

just ignore? ... or is there a later version that has not been updated to git? ...

#crysx

if you are compiling from git, you can do a git pull and that will go away. it was fixed about an hour ago. the next wallet releases will be updated in a few days..

an hour ago? ... no worries ...

recompiling again ...

new wallet? ... is this not the new wallet? ... with multialgo? ...

#crysx

btw - the latest git does not compile ... bombs out with errors ...

Code:

/usr/bin/ar -rs libleveldb.a db/builder.o db/c.o db/dbformat.o db/db_impl.o db/db_iter.o db/filename.o db/log_reader.o db/log_writer.o db/memtable.o db/repair.o db/table_cache.o db/version_edit.o db/version_set.o db/write_batch.o table/block_builder.o table/block.o table/filter_block.o table/format.o table/iterator.o table/merger.o table/table_builder.o table/table.o table/two_level_iterator.o util/arena.o util/bloom.o util/cache.o util/coding.o util/comparator.o util/crc32c.o util/env.o util/env_posix.o util/env_win.o util/filter_policy.o util/hash.o util/histogram.o util/logging.o util/options.o util/status.o port/port_posix.o
/usr/bin/ar: creating libleveldb.a
make[2]: Leaving directory '/mnt/horustor/compile/coins/vergecurrency/VERGE/src/leveldb'
  CXXLD    VERGEd
libbitcoin_server.a(libbitcoin_server_a-rpcmining.o): In function `getmininginfo(std::vector, std::allocator > > >, std::allocator, std::allocator > > > > > const&, bool)':
/mnt/horustor/compile/coins/vergecurrency/VERGE/src/rpcmining.cpp:75: undefined reference to `GetDifficulty(CBlockIndex const*)'
libbitcoin_wallet.a(libbitcoin_wallet_a-rpcwallet.o): In function `getinfo(std::vector, std::allocator > > >, std::allocator, std::allocator > > > > > const&, bool)':
/mnt/horustor/compile/coins/vergecurrency/VERGE/src/rpcwallet.cpp:86: undefined reference to `GetDifficulty(CBlockIndex const*)'
collect2: error: ld returned 1 exit status
Makefile:1619: recipe for target 'VERGEd' failed
make[1]: *** [VERGEd] Error 1
make[1]: Leaving directory '/mnt/horustor/compile/coins/vergecurrency/VERGE/src'
Makefile:523: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

obviously this shows VERGEd not being compiled here - but the bombout is with VERGE-qt also ...

#crysx

it looks like you don't have a correct git tree.
try re-cloning from scratch.

its from the main git pallas ...

go to the git and see ...

ive changed nothing from the clone i did before it - which did compile ... git pull showed there were updates - so i cloned again and compiled and had these errors ...

#crysx

read my post just over yours.
git compiles fine, I even fixed it.

in the current git now? ...

if so - ill clone again now and recompile ...

#crysx

crysx

sr. member

Activity: 364

Merit: 260

--- ChainWorks Industries ---

yeah its good to go. starting to work on the getdifficulty rpc command for each algo. not finished, but the commits that are new do work.

try git pull and make clean.

our README page on the source code, includes a build pass/fail tag. it is built automatically after each commit/pull request to make sure it doesn't break.

this link will let you know if our current build in the master branch works or not, as the build process is logged from start to finish, and available to see =]

https://travis-ci.org/vergecurrency/VERGE

ill be speaking with pool admins over the next day or two to see how mining is going on their end, see if they have anything they'd like to see tweaked etc,

and setting up an x17/blake2s pool, with 2% fee that goes to development ;p

ps: cryptsy is not in control of their funds anymore, they tried to send coins to bittrex and they were halted and sent to a management company, so i dont

think we need to worry about a massive dump from cryptsy, plus ALOT of our users (and other users) got xvg out of there before they closed. i dont think they

had very many when they closed.

this is where im getting the clone from and still the same output after compile - https://github.com/vergecurrency/VERGE ...

ill have another go at it - but im getting weary of it :| ...

#crysx

pallas

legendary

Activity: 2716

Merit: 1094

Black Belt Developer

Quote from: crysx on April 12, 2016, 06:58:34 AM

Quote from: pallas on April 12, 2016, 04:48:43 AM

Quote from: Dogedarkdev on April 11, 2016, 10:38:13 PM

Quote from: pallas on April 12, 2016, 04:48:43 AM

hi all ...

after compiling from the git ( yesterday ) - the wallet STILL says 'warning: this version is obsolete, upgrade required' ...

just ignore? ... or is there a later version that has not been updated to git? ...

#crysx

if you are compiling from git, you can do a git pull and that will go away. it was fixed about an hour ago. the next wallet releases will be updated in a few days..

an hour ago? ... no worries ...

recompiling again ...

new wallet? ... is this not the new wallet? ... with multialgo? ...

#crysx

btw - the latest git does not compile ... bombs out with errors ...

Code:

/usr/bin/ar -rs libleveldb.a db/builder.o db/c.o db/dbformat.o db/db_impl.o db/db_iter.o db/filename.o db/log_reader.o db/log_writer.o db/memtable.o db/repair.o db/table_cache.o db/version_edit.o db/version_set.o db/write_batch.o table/block_builder.o table/block.o table/filter_block.o table/format.o table/iterator.o table/merger.o table/table_builder.o table/table.o table/two_level_iterator.o util/arena.o util/bloom.o util/cache.o util/coding.o util/comparator.o util/crc32c.o util/env.o util/env_posix.o util/env_win.o util/filter_policy.o util/hash.o util/histogram.o util/logging.o util/options.o util/status.o port/port_posix.o
/usr/bin/ar: creating libleveldb.a
make[2]: Leaving directory '/mnt/horustor/compile/coins/vergecurrency/VERGE/src/leveldb'
  CXXLD    VERGEd
libbitcoin_server.a(libbitcoin_server_a-rpcmining.o): In function `getmininginfo(std::vector, std::allocator > > >, std::allocator, std::allocator > > > > > const&, bool)':
/mnt/horustor/compile/coins/vergecurrency/VERGE/src/rpcmining.cpp:75: undefined reference to `GetDifficulty(CBlockIndex const*)'
libbitcoin_wallet.a(libbitcoin_wallet_a-rpcwallet.o): In function `getinfo(std::vector, std::allocator > > >, std::allocator, std::allocator > > > > > const&, bool)':
/mnt/horustor/compile/coins/vergecurrency/VERGE/src/rpcwallet.cpp:86: undefined reference to `GetDifficulty(CBlockIndex const*)'
collect2: error: ld returned 1 exit status
Makefile:1619: recipe for target 'VERGEd' failed
make[1]: *** [VERGEd] Error 1
make[1]: Leaving directory '/mnt/horustor/compile/coins/vergecurrency/VERGE/src'
Makefile:523: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

obviously this shows VERGEd not being compiled here - but the bombout is with VERGE-qt also ...

#crysx

it looks like you don't have a correct git tree.
try re-cloning from scratch.

its from the main git pallas ...

go to the git and see ...

ive changed nothing from the clone i did before it - which did compile ... git pull showed there were updates - so i cloned again and compiled and had these errors ...

#crysx

read my post just over yours.
git compiles fine, I even fixed it.

crysx

sr. member

Activity: 364

Merit: 260

--- ChainWorks Industries ---

Quote from: Dogedarkdev on April 11, 2016, 10:38:13 PM

hi all ...

after compiling from the git ( yesterday ) - the wallet STILL says 'warning: this version is obsolete, upgrade required' ...

just ignore? ... or is there a later version that has not been updated to git? ...

#crysx

if you are compiling from git, you can do a git pull and that will go away. it was fixed about an hour ago. the next wallet releases will be updated in a few days..

an hour ago? ... no worries ...

recompiling again ...

new wallet? ... is this not the new wallet? ... with multialgo? ...

#crysx

btw - the latest git does not compile ... bombs out with errors ...

Code:

/usr/bin/ar -rs libleveldb.a db/builder.o db/c.o db/dbformat.o db/db_impl.o db/db_iter.o db/filename.o db/log_reader.o db/log_writer.o db/memtable.o db/repair.o db/table_cache.o db/version_edit.o db/version_set.o db/write_batch.o table/block_builder.o table/block.o table/filter_block.o table/format.o table/iterator.o table/merger.o table/table_builder.o table/table.o table/two_level_iterator.o util/arena.o util/bloom.o util/cache.o util/coding.o util/comparator.o util/crc32c.o util/env.o util/env_posix.o util/env_win.o util/filter_policy.o util/hash.o util/histogram.o util/logging.o util/options.o util/status.o port/port_posix.o
/usr/bin/ar: creating libleveldb.a
make[2]: Leaving directory '/mnt/horustor/compile/coins/vergecurrency/VERGE/src/leveldb'
  CXXLD    VERGEd
libbitcoin_server.a(libbitcoin_server_a-rpcmining.o): In function `getmininginfo(std::vector, std::allocator > > >, std::allocator, std::allocator > > > > > const&, bool)':
/mnt/horustor/compile/coins/vergecurrency/VERGE/src/rpcmining.cpp:75: undefined reference to `GetDifficulty(CBlockIndex const*)'
libbitcoin_wallet.a(libbitcoin_wallet_a-rpcwallet.o): In function `getinfo(std::vector, std::allocator > > >, std::allocator, std::allocator > > > > > const&, bool)':
/mnt/horustor/compile/coins/vergecurrency/VERGE/src/rpcwallet.cpp:86: undefined reference to `GetDifficulty(CBlockIndex const*)'
collect2: error: ld returned 1 exit status
Makefile:1619: recipe for target 'VERGEd' failed
make[1]: *** [VERGEd] Error 1
make[1]: Leaving directory '/mnt/horustor/compile/coins/vergecurrency/VERGE/src'
Makefile:523: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

obviously this shows VERGEd not being compiled here - but the bombout is with VERGE-qt also ...

#crysx

it looks like you don't have a correct git tree.
try re-cloning from scratch.

its from the main git pallas ...

go to the git and see ...

ive changed nothing from the clone i did before it - which did compile ... git pull showed there were updates - so i cloned again and compiled and had these errors ...

#crysx

pallas

legendary

Activity: 2716

Merit: 1094

Black Belt Developer

I think I fixed the wallet mining, the diff reporting and the broken algos.
There are at least two bugs.
Unfortunately I can't test the block generation because the network is refusing my x17 blocks.

EDIT: do you want me to submit a pull request with the fixes?

EDIT2: a hard fork is necessary to fix x17 and blake2s; they won't work unless most wallets are upgraded.

Dogedarkdev

legendary

Activity: 1708

Merit: 1009

$XVG - The Standard in Crypto as a Currency!

yeah its good to go. starting to work on the getdifficulty rpc command for each algo. not finished, but the commits that are new do work.

try git pull and make clean.

our README page on the source code, includes a build pass/fail tag. it is built automatically after each commit/pull request to make sure it doesn't break.

this link will let you know if our current build in the master branch works or not, as the build process is logged from start to finish, and available to see =]

https://travis-ci.org/vergecurrency/VERGE

ill be speaking with pool admins over the next day or two to see how mining is going on their end, see if they have anything they'd like to see tweaked etc,

and setting up an x17/blake2s pool, with 2% fee that goes to development ;p

ps: cryptsy is not in control of their funds anymore, they tried to send coins to bittrex and they were halted and sent to a management company, so i dont

think we need to worry about a massive dump from cryptsy, plus ALOT of our users (and other users) got xvg out of there before they closed. i dont think they

had very many when they closed.

pallas

legendary

Activity: 2716

Merit: 1094

Black Belt Developer

Quote from: Dogedarkdev on April 11, 2016, 10:38:13 PM