Personaly i don't like Lyra2REv2 but mayby this is good thing for Lyrabar..
Topic: [ANN] Lyrabar - A rare bar with Lyra2REv2 algorithm, 0.9.1 is out! [CPU/GPU PoW] - page 9. (Read 67665 times)
November 05, 2015, 01:09:03 PM
Lyrabar and CPU mining is allmost dead now
Personaly i don't like Lyra2REv2 but mayby this is good thing for Lyrabar..
Personaly i don't like Lyra2REv2 but mayby this is good thing for Lyrabar..
November 05, 2015, 12:53:41 PM
Made my poll choice: GPU for sure, sorry but CPU mining is too obsolete!
November 05, 2015, 12:50:08 PM
Under 700 blocks to new algo! Looking nice 
November 01, 2015, 11:20:38 PM
the new wallet works great wooohoo lyrabar!!! 
Great, if anyone facing any kind of issue like crash or a error, report immediately, last lines are the newest in the logging system, the debug.log is good to see if problems show up.
Its located on Windows systems at
Code:
Users//AppData/Roaming/Lyrabar/debug.log
On GNU/Linux systems, the wallet's data diretory is at user's home directory,
Code:
~/.lyrabar/ (or /home//.lyrabar)
November 01, 2015, 11:14:22 PM
Wallet updated and synced!
I have removed the wallet downloads from Lyrabar.us, and I've replaced them with a link to this topic so people can always find the latest official download.
I have removed the wallet downloads from Lyrabar.us, and I've replaced them with a link to this topic so people can always find the latest official download.
Thanks! Such activity, I like the community we have alot
November 01, 2015, 10:48:23 PM
the new wallet works great wooohoo lyrabar!!!
November 01, 2015, 10:41:20 PM
Wallet updated and synced!
I have removed the wallet downloads from Lyrabar.us, and I've replaced them with a link to this topic so people can always find the latest official download.
I have removed the wallet downloads from Lyrabar.us, and I've replaced them with a link to this topic so people can always find the latest official download.
November 01, 2015, 10:18:17 PM
Lyrabar Windows Qt wallet 0.9.1, 32-bits version is here ready for downloading:
Windows, 32-bit (daemon incl.) http://lyrabar.duckdns.org/releases/Lyrabar-0.9.1-win32.rar
(With openssl 1.0.2d, Qt 5, compiled in Windows 10 Pro x64)
Please update, this is a mandatory patch for Lyrabar. Algorithm will change to Lyra2REv2 at block 160000.
Feel free to give feedback about new wallets!
Windows, 32-bit (daemon incl.) http://lyrabar.duckdns.org/releases/Lyrabar-0.9.1-win32.rar
(With openssl 1.0.2d, Qt 5, compiled in Windows 10 Pro x64)
Please update, this is a mandatory patch for Lyrabar. Algorithm will change to Lyra2REv2 at block 160000.
Feel free to give feedback about new wallets!
October 31, 2015, 12:34:50 PM
my mistake - i'm used lyra2v2 before 160000, thanks
Glad to hear you managed to get it work!
Happy mining! 
October 31, 2015, 11:29:47 AM
not working - only "low difficulty share" appear in miner
I can help with problems, if you supply more information about your mining hardware and software you are using.
I assume you are using a GPU miner, so:
If using AMD, You need to use latest djm34's sgminer. If using NVIDIA, use latest ccminer by tpruvot & djm34. Do not use manual difficulty adjustments like "--diff-multiplier", the stratum poolserver algorithm multiplier is adjusted right on the official pool. Make sure you are using Lyra2RE algorithm before block 160000, Lyra2REv2 algorithm after block 160000.
On sgminer, the algorithm names are with uppercase letters needed, "Lyra2RE" and "Lyra2REv2".
On ccminer, the algorithm names are not with uppercase letters, "lyra2" and "lyra2re2", this also applies on tpruvot's cpuminer-multi cpuminer software.
Wrong miner software configurations are the most common problems with Lyra2RE and Lyra2REv2 algorithms. Also, remember not to use too high intensity or xintensity.
Hope this helps you and hope people will read the guides and manuals before complaining.
my mistake - i'm used lyra2v2 before 160000, thanks
October 30, 2015, 09:27:17 AM
not working - only "low difficulty share" appear in miner
I can help with problems, if you supply more information about your mining hardware and software you are using.
I assume you are using a GPU miner, so:
If using AMD, You need to use latest djm34's sgminer. If using NVIDIA, use latest ccminer by tpruvot & djm34. Do not use manual difficulty adjustments like "--diff-multiplier", the stratum poolserver algorithm multiplier is adjusted right on the official pool. Make sure you are using Lyra2RE algorithm before block 160000, Lyra2REv2 algorithm after block 160000.
On sgminer, the algorithm names are with uppercase letters needed, "Lyra2RE" and "Lyra2REv2".
On ccminer, the algorithm names are not with uppercase letters, "lyra2" and "lyra2re2", this also applies on tpruvot's cpuminer-multi cpuminer software.
Wrong miner software configurations are the most common problems with Lyra2RE and Lyra2REv2 algorithms. Also, remember not to use too high intensity or xintensity.
Hope this helps you and hope people will read the guides and manuals before complaining.
October 28, 2015, 11:55:41 PM
Official pool is again up and finding blocks with the new wallet like should!
Join the fun,
http://lyrabarpool.duckdns.org/
Join the fun,
http://lyrabarpool.duckdns.org/
not working - only "low difficulty share" appear in miner
October 25, 2015, 05:06:14 PM
Official pool is again up and finding blocks with the new wallet like should!
Join the fun,
http://lyrabarpool.duckdns.org/
Join the fun,
http://lyrabarpool.duckdns.org/
October 25, 2015, 01:06:46 PM
Because of the suspicious behaviour of many coins' Windows wallets lately (viruses and similar stuff), I tell this only once, If anyone posts a Windows wallet in here than me, You use it at own risk.
I'm providing the official Windows wallet so no one's coins gets stolen or computer does not get infected or anything because of wallets with that kind of behaviour.
I'm providing the official Windows wallet so no one's coins gets stolen or computer does not get infected or anything because of wallets with that kind of behaviour.
Thanks, and I'll just link to here at Lyrabar.us instead of hosting the new wallets there. That way there's no confusion about any other links being the official wallet.
-edit-
This is runpaint, mis-using the official dev account of BARR. I forgot to switch to my own account, whoops
October 25, 2015, 12:21:00 PM
Because of the suspicious behaviour of many coins' Windows wallets lately (viruses and similar stuff), I tell this only once, If anyone posts a Windows wallet in here other than me, You use it at own risk.
I'm providing the official Windows wallet so no one's coins gets stolen or computer does not get infected or anything because of wallets with that kind of behaviour.
Linux amd64 daemon + Qt wallet, with elder libstdc++ and openssl 1.0.1f
http://lyrabar.duckdns.org/releases/lyrabar-0.9.1-amd64.tar
Linux amd64 daemon + Qt wallet, with newer libstdc++ and openssl 1.0.2d
http://lyrabar.duckdns.org/releases/lyrabar-0.9.1-amd64-new-stdc.tar
Linux i386 daemon + Qt wallet, with elder libstdc++ and openssl 1.0.1k
http://lyrabar.duckdns.org/releases/lyrabar-0.9.1-i386.tar
Version with elder libraries will work for sure if the newest one doesn't. All the wallets are compiled with Berkeley DB 4.8, elder ones with libstdc++6 3.4.20 and newer ones with 3.4.21. You can check your libstdc++ version in amd64 systems by command Where "x86_64-linux-gnu" is the system arch. More guidance in the README.md (updating it soon)
I'm providing the official Windows wallet so no one's coins gets stolen or computer does not get infected or anything because of wallets with that kind of behaviour.
Linux amd64 daemon + Qt wallet, with elder libstdc++ and openssl 1.0.1f
http://lyrabar.duckdns.org/releases/lyrabar-0.9.1-amd64.tar
Linux amd64 daemon + Qt wallet, with newer libstdc++ and openssl 1.0.2d
http://lyrabar.duckdns.org/releases/lyrabar-0.9.1-amd64-new-stdc.tar
Linux i386 daemon + Qt wallet, with elder libstdc++ and openssl 1.0.1k
http://lyrabar.duckdns.org/releases/lyrabar-0.9.1-i386.tar
Version with elder libraries will work for sure if the newest one doesn't. All the wallets are compiled with Berkeley DB 4.8, elder ones with libstdc++6 3.4.20 and newer ones with 3.4.21. You can check your libstdc++ version in amd64 systems by command
Code:
strings /usr/lib/x86_64-linux-gnu/libstdc++.so.6 | grep GLIBCXX
October 25, 2015, 12:13:01 PM
You were fast,
I got the same error using current libsecp256k1 when trying to compile old wallet, new wallet didn't have that error because it's fixed on the 0.9.1.
Double make sure you are on the right secp256k1 commit:
cd /opt
git clone https://github.com/bitcoin/secp256k1
cd secp256k1
git checkout 4c63780710351ffcc52341497e3ca0e518fbad79
./autogen.sh
./configure
make
make install
Update the LD cache to tell the system about the freshly installed secp256k1 existence,
ldconfig (or ld-config)
Posting soon linux wallets, which are compiled with latest openssl 1.0.2d and libstdc++ on Debian 9.
Will also post links of version compiled with elder libstdc++ to make sure everyone with ubuntu 15.04 and elder systems can run it.
Windows wallet tomorrow, building the Windows 32bit compilation environment at the moment.
Old wallets can hear new ones, so no panic until block 160000 is near.
I got the same error using current libsecp256k1 when trying to compile old wallet, new wallet didn't have that error because it's fixed on the 0.9.1.
Double make sure you are on the right secp256k1 commit:
cd /opt
git clone https://github.com/bitcoin/secp256k1
cd secp256k1
git checkout 4c63780710351ffcc52341497e3ca0e518fbad79
./autogen.sh
./configure
make
make install
Update the LD cache to tell the system about the freshly installed secp256k1 existence,
ldconfig (or ld-config)
Posting soon linux wallets, which are compiled with latest openssl 1.0.2d and libstdc++ on Debian 9.
Will also post links of version compiled with elder libstdc++ to make sure everyone with ubuntu 15.04 and elder systems can run it.
Windows wallet tomorrow, building the Windows 32bit compilation environment at the moment.
Old wallets can hear new ones, so no panic until block 160000 is near.
October 25, 2015, 10:25:32 AM
Trying to build the new wallet (after installing secp256k1):
In file included from src/main.h:13:0,
from src/wallet.h:13,
from src/init.h:8,
from src/qt/signverifymessagedialog.cpp:11:
src/stealth.h:159:5: error: ‘secp256k1_context_t’ does not name a type
secp256k1_context_t* getContext()
^
src/stealth.h:166:5: error: ‘secp256k1_context_t’ does not name a type
secp256k1_context_t* ctx;
^
src/stealth.h: In destructor ‘init_singleton::~init_singleton()’:
src/stealth.h:150:39: error: ‘ctx’ was not declared in this scope
secp256k1_context_destroy(ctx);
^
src/stealth.h: In member function ‘void init_singleton::init()’:
src/stealth.h:156:9: error: ‘ctx’ was not declared in this scope
ctx = secp256k1_context_create(SECP256K1_CONTEXT_SIGN | SECP256K1_CONTEXT_VERIFY);
^
Makefile:1153: recipe for target 'build/script.o' failed
In file included from src/main.h:13:0,
from src/wallet.h:13,
from src/init.h:8,
from src/qt/signverifymessagedialog.cpp:11:
src/stealth.h:159:5: error: ‘secp256k1_context_t’ does not name a type
secp256k1_context_t* getContext()
^
src/stealth.h:166:5: error: ‘secp256k1_context_t’ does not name a type
secp256k1_context_t* ctx;
^
src/stealth.h: In destructor ‘init_singleton::~init_singleton()’:
src/stealth.h:150:39: error: ‘ctx’ was not declared in this scope
secp256k1_context_destroy(ctx);
^
src/stealth.h: In member function ‘void init_singleton::init()’:
src/stealth.h:156:9: error: ‘ctx’ was not declared in this scope
ctx = secp256k1_context_create(SECP256K1_CONTEXT_SIGN | SECP256K1_CONTEXT_VERIFY);
^
Makefile:1153: recipe for target 'build/script.o' failed
October 21, 2015, 05:04:49 PM
What I really wish to know is when the algo switch will be.
Very sorry for the late answer. The algorithm change will be at block 160000, so the block 160001 will be the very first Lyra2REv2 block. In timescale, ~2 weeks until the algorithm changes.
Will post 0.9.1 sources and binaries this week, naturally also adding them to the first post.
Everyone can consider this as a notification of the new 0.9.1 wallet incoming this week.
Will contact exchange(s) and pool(s) to remind them about new wallet incoming because new wallets do not hear old ones and vice versa (adjustments in the protocol).
More info upcoming during this and next week
October 14, 2015, 04:36:02 PM
What I really wish to know is when the algo switch will be.
October 14, 2015, 04:31:53 PM
Interesting i may mine this
Jump to: