[ANN] GirlsToken-2.0 - 2.3-ALPHA in testing now[ANN]

[wildbud]

There will be no anymore "BIG BLOCKS" after 450k?

[l8nit3]

There will be no anymore "BIG BLOCKS" after 450k?

You are correct, also POS percent will drop from 10% to 2.5%

[Redni]

I have fews XGTC on my wallet.dat from previous source and I use Linux. Salvage wallet not available on Linux?

[l8nit3]

I have fews XGTC on my wallet.dat from previous source and I use Linux. Salvage wallet not available on Linux?

Are you using a daemon or the qt wallet? Also do you use prebuilt or build yourself?
<edit>
If you build yourself (qt or daemon) then there should be no issues as you will be building with the same BDB version as you did originally (I assume). The only reason there was an issue for some was that the pre-built qt wallet was built with BDB 6.1.26 whereas I use the standard 4.8.30NC. So long as you are using the same build machine you should be safe

[Redni]

I have fews XGTC on my wallet.dat from previous source and I use Linux. Salvage wallet not available on Linux?

Are you using a daemon or the qt wallet? Also do you use prebuilt or build yourself?

Own Qt Wallet prebuild from this topic and source: https://bitcointalk.org/index.php?topic=1788321.0. From deamons I can also use. I do not know what you're asking?

[l8nit3]

I have fews XGTC on my wallet.dat from previous source and I use Linux. Salvage wallet not available on Linux?

Are you using a daemon or the qt wallet? Also do you use prebuilt or build yourself?

Own Qt Wallet prebuild from this topic and source: https://bitcointalk.org/index.php?topic=1788321.0. From deamons I can also use. I do not know what you're asking?

Ok so you are completing your own build from source. Which means all of the requirements (boost bdbd openssl) will be the same. open your original wallet and use the "dumpprivkey" command to back up your priv key just in case. Then complete a build in the same way you did before (following the tutorial you provided).
Here are the deps I use, however I'm unsure what was used for BDB for the old Linux qt as I was not the one who built it.

Code:

sudo apt-get install libdb5.1-dev libdb5.1++-dev libboost-all-dev libqrencode-dev qt4-qmake libqt4-dev build-essential libboost-dev libboost-system-dev libboost-filesystem-dev libboost-program-options-dev libboost-thread-dev libssl-dev automake

Just to be sure, here is the method for compiling the Linux qt wallet:
1) Download and unpack the source code.
2) run the command  

Code:

cd src && make -f makefile.unix

to build daemon first
3) run the command  

Code:

cd ../ && qmake-qt4 "USE_UPNP=1" "USE_IPV6=1" "USE_QRCODE=1" girlstoken-qt.pro && make

to finally build the qt wallet.

If you still have issue please let me know and we will get them worked out for you

[Redni]

Thanks Small fix: https://github.com/l8nit3tr0ubl3/GirlsToken-2.0/pull/5

[l8nit3]

Thanks Small fix: https://github.com/l8nit3tr0ubl3/GirlsToken-2.0/pull/5

I see that thank you
Will test asap and then merge 😁
<edit>
merged and will be included in next release

[Redni]

I try create own graphic for GirlsToken. Maybe someone will like it.



BASED ON: http://www.freepik.com/free-vector/astonished-girl-with-virtual-reality_1041269.htm

[l8nit3]

Interesting design we will let the community decide

[kruanko]

Coinexchange wallet up to date

[l8nit3]

Coinexchange wallet up to date

I just saw that aswell!! I will update the OP. 

[Redni]

     
     ↝  GirlsToken | Torrent SnapShot  ↜

     Why SnapShot and why Torrent? 

     
     ☺  Speed and no waiting, after downloading, just copy the files to have the current block chain.
     ☺  Ability to safely intercept the download and resume it.
     ☺  Additional Nodes and Peers attached.
     ☺  Updates every few days.
    

     Last Update: 14.08.2017:14.40 UTC+01:00  

     Donations: GZdA2bsjap6cBXD3c2ps9ZM6pEgp7oj1kg  

[l8nit3]

     
     ↝  GirlsToken | Torrent SnapShot  ↜

     Why SnapShot and why Torrent? 

     
     ☺  Speed and no waiting, after downloading, just copy the files to have the current block chain.
     ☺  Ability to safely intercept the download and resume it.
     ☺  Additional Nodes and Peers attached.
     ☺  Updates every few days.
    

     Last Update: 14.08.2017:14.40 UTC+01:00  

     Donations: GZdA2bsjap6cBXD3c2ps9ZM6pEgp7oj1kg  

Wonderful, thank you for your help I am also uploading an updated bootstrap now

[Ethereuming]

I can't open the mac wallet. 

[l8nit3]

I can't open the mac wallet.  

what version of mac and what version of the wallet? the 2.1.12 version? also is there an error message by chance?

[Ethereuming]

I can't open the mac wallet.  

what version of mac and what version of the wallet? the 2.1.12 version? also is there an error message by chance?

The mac is not very new: MAC OS X 10.6.8
 yes 2.1.1.2 version
Yes error message, I can't open the file.

[l8nit3]

The mac is not very new...MAC OS X 10.6.8
 yes 2.1.1.2 version
Yes error message...

Ahhh that is the issue there. Due to enabling qrcode support, a minimum of version 10.7 is required. I apologize, and will build a version compatible with older versions as soon as i am off work 9pm est.

[Ethereuming]

The mac is not very new...MAC OS X 10.6.8
 yes 2.1.1.2 version
Yes error message...

Ahhh that is the issue there. Due to enabling qrcode support, a minimum of version 10.7 is required. I apologize, and will build a version compatible with older versions as soon as i am off work 9pm est.

Ok dev, I wait...
Thanks 

[l8nit3]

The mac is not very new...MAC OS X 10.6.8
 yes 2.1.1.2 version
Yes error message...

Ahhh that is the issue there. Due to enabling qrcode support, a minimum of version 10.7 is required. I apologize, and will build a version compatible with older versions as soon as i am off work 9pm est.

Ok dev, I wait...
Thanks  

Ok, so it seems I was incorrect in remembering why the wallet needed to be compiled with 10.7+ as a base. It was not qrcode support, but was libc++11. It would seem that Apple has decided to only officially support libc++ on 10.7... so I will have to add an hdd to my hackintosh [or possibly just a VM] and setup a 10.6.8 build to be able to properly compile for versions 10.7 and under.
All this is to say, I am working on it but may take a bit longer then a simple re-compile as I originally thought.