Bitcoin Forum
December 18, 2017, 01:48:30 PM *
News: Latest stable version of Bitcoin Core: 0.15.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 [26] 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 ... 92 »
  Print  
Author Topic: Slimcoin | First Proof of Burn currency | New v0.5.1 binaries  (Read 88258 times)
d5000
Legendary
*
Offline Offline

Activity: 1582



View Profile
March 31, 2017, 05:23:24 PM
 #501

I've compiled the newest version now with the transcription error fix, but in Ubuntu 14.04 with Boost 1.58 (parallel install to 1.54) it still crashes after the first CBlock message in the debug.log. Maybe it's simply too old :-/ but it is a LTS and that's why I chose it for my VPS back in 2015.

Ah, I forgot, just a comment to the GUI changes. I think the Burn coins button should continue to be visible in the main window. It may be little used but Proof of Burn is the unique feature of Slimcoin, so the symbol would visually reinforce the "brand". I've also thought on a renewed Slimcoin logo with a stylized flame replacing the "i-point" as a hint to PoB. Just an opinion.



       ▀
   ▄▄▄   ▄▀
   ███ ▄▄▄▄  ██
       ████
    ▄  ▀▀▀▀
▄▄
      ██    ▀▀
██▄█▄▄▄████████
▄▄▄▄▄▄▄▄▀▀███▀▀▀
██████████████████
████▄▀▄▀▄▀███▀▀▀▀▀
████▄▀▄▀▄▀███ ▀
████▄▀▄▀▄▀████████
▀█████████████████
]
,CoinPayments,
█████
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████
█████
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████
█████
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████
1513604910
Hero Member
*
Offline Offline

Posts: 1513604910

View Profile Personal Message (Offline)

Ignore
1513604910
Reply with quote  #2

1513604910
Report to moderator
1513604910
Hero Member
*
Offline Offline

Posts: 1513604910

View Profile Personal Message (Offline)

Ignore
1513604910
Reply with quote  #2

1513604910
Report to moderator
1513604910
Hero Member
*
Offline Offline

Posts: 1513604910

View Profile Personal Message (Offline)

Ignore
1513604910
Reply with quote  #2

1513604910
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1513604910
Hero Member
*
Offline Offline

Posts: 1513604910

View Profile Personal Message (Offline)

Ignore
1513604910
Reply with quote  #2

1513604910
Report to moderator
1513604910
Hero Member
*
Offline Offline

Posts: 1513604910

View Profile Personal Message (Offline)

Ignore
1513604910
Reply with quote  #2

1513604910
Report to moderator
resor
Newbie
*
Offline Offline

Activity: 14


View Profile
March 31, 2017, 05:28:10 PM
 #502

Srry for bothering where i can learn how to use CLI slimcoind
gjhiggins
Legendary
*
Offline Offline

Activity: 1218



View Profile WWW
March 31, 2017, 06:08:45 PM
 #503

Srry for bothering where i can learn how to use CLI slimcoind

It's no bother, it's why this thread exists Smiley

You can open the debug window, select the console tab and type help on the built-in console which results in the following list of commands ...

Code:
addmultisigaddress <nrequired> <'["key","key"]'> [account]
backupwallet <destination>
burncoins <fromaccount> <amount> [minconf=1] [comment] [comment-to]
calcburnhash [fPrintRegardless=false]
checkwallet
dumpprivkey <slimcoinaddress>
encryptwallet <passphrase>
getaccount <slimcoinaddress>
getaccountaddress <account>
getaddressesbyaccount <account>
getbalance [account] [minconf=1]
getblock <hash> [txinfo]
getblockcount
getblockhash <index>
getblocktemplate [params]
getburndata
getcheckpoint
getconnectioncount
getdifficulty
getgenerate
gethashespersec
getinfo
getmemorypool [data]
getmininginfo
getnetworkghps
getnewaddress [account]
getpeerinfo
getrawtransaction <txid> [verbose=0]
getreceivedbyaccount <account> [minconf=1]
getreceivedbyaddress <slimcoinaddress> [minconf=1]
gettransaction <txid>
getwork [data]
help [command]
importpassphrase "<passphrase>" [label]
importprivkey <slimcoinprivkey> [label]
keypoolrefill
listaccounts [minconf=1]
listburnminted [verbose=false]
listreceivedbyaccount [minconf=1] [includeempty=false]
listreceivedbyaddress [minconf=1] [includeempty=false]
listsinceblock [blockhash] [target-confirmations]
listtransactions [account="*"] [fBurnTx=false] [count=10] [from=0]
makekeypair [prefix]
move <fromaccount> <toaccount> <amount> [minconf=1] [comment]
repairwallet
reservebalance [<reserve> [amount]]
sendalert <message> <privatekey> <minver> <maxver> <priority> <id> [cancelupto]
sendfrom <fromaccount> <toslimcoinaddress> <amount> [minconf=1] [comment] [comment-to]
sendmany <fromaccount> {address:amount,...} [minconf=1] [comment]
sendrawtransaction <hex string>
sendtoaddress <slimcoinaddress> <amount> [comment] [comment-to]
setaccount <slimcoinaddress> <account>
setgenerate <generate> [genproclimit]
settxfee <amount>
signmessage <slimcoinaddress> <message>
signrawtransaction <hex string> [{"txid":txid,"vout":n,"scriptPubKey":hex},...] [<privatekey1>,...] [sighashtype="ALL"]
stop
submitblock <hex data> [optional-params-obj]
validateaddress <slimcoinaddress>
verifymessage <slimcoinaddress> <signature> <message>

Detailed help on each command is available by typing help <command>, e.g. help submitblock

Code:
submitblock <hex data> [optional-params-obj]
[optional-params-obj] parameter is currently ignored.
Attempts to submit new block to network.
See https://en.bitcoin.it/wiki/BIP_0022 for full specification.

(You can also use the CLI with the headless daemon by setting listen=1 in the config file and then ./slimcoind help submitblock for example).

BTW, there's a list of command-line options at the foot of the master branch's README file https://github.com/slimcoin-project/Slimcoin/blob/master/README.md

HTH

Cheers

Graham

Edit: added README ref
resor
Newbie
*
Offline Offline

Activity: 14


View Profile
March 31, 2017, 07:06:02 PM
 #504

Sorry, but i only have these commands

  http://imgur.com/Hvzf77il.png
d5000
Legendary
*
Offline Offline

Activity: 1582



View Profile
March 31, 2017, 07:13:05 PM
 #505

Sorry, but i only have these commands

  


These are the command line options. The RPC commands will be available if you run the slimcoind daemon:

Code:
slimcoind -daemon -listen=1

and then in the same terminal, type:

Code:
slimcoind help

(Basically, it's the same like the Peercoin daemon - with the exception of the specific Proof of Burn messages like getburndata - , maybe there is more documentation about it.)




       ▀
   ▄▄▄   ▄▀
   ███ ▄▄▄▄  ██
       ████
    ▄  ▀▀▀▀
▄▄
      ██    ▀▀
██▄█▄▄▄████████
▄▄▄▄▄▄▄▄▀▀███▀▀▀
██████████████████
████▄▀▄▀▄▀███▀▀▀▀▀
████▄▀▄▀▄▀███ ▀
████▄▀▄▀▄▀████████
▀█████████████████
]
,CoinPayments,
█████
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████
█████
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████
█████
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████
resor
Newbie
*
Offline Offline

Activity: 14


View Profile
March 31, 2017, 08:28:19 PM
 #506

Now it says this :
"blockchain redownload required approaching or past v0.4 upgrade deadline."
ArchitektoR
Full Member
***
Offline Offline

Activity: 122


View Profile
April 02, 2017, 10:09:53 AM
 #507


Thanks again for all your slimcoin work and updates! Can you please provide your SLM address so I can send some SLM as a donation or bounties or a thanks?
gjhiggins
Legendary
*
Offline Offline

Activity: 1218



View Profile WWW
April 02, 2017, 12:38:52 PM
 #508

Now it says this :
"blockchain redownload required approaching or past v0.4 upgrade deadline."

The warning is a harmless inheritance from the Peercoin code:

https://github.com/slimcoin-project/Slimcoin/blob/slimcoin/src/main.cpp#L3238

and there seems no objection to my suggestion of removing it from the Slimcoin 0.4.[0|1] codebase.

The warning doesn't appear in the 0.5.0 version of Slimcoin that I am preparing for contribution.

Cheers

Graham
gjhiggins
Legendary
*
Offline Offline

Activity: 1218



View Profile WWW
April 02, 2017, 01:25:46 PM
 #509

Whilst hunting around for the meaning of stealth_version_byte (a bitcoin address prefix, it transpires), I found the following summary of stealth addresses/transactions on Bitcoin stackexchange:

Quote
As I understand it, the "stealth address" is intended to address a very specific problem. If you wish to solicit payments from the public, say by posting a donation address on your website, then everyone can see on the block chain that all those payments went to you, and perhaps try to track how you spend them.

With a stealth address, you ask payers to generate a unique address in such a way that you (using some additional data which is attached to the transaction) can deduce the corresponding private key. So although you publish a single "stealth address" on your website, the block chain sees all your incoming payments as going to separate addresses and has no way to correlate them. (Of course, any individual payer knows their payment went to you, and can trace how you spend it, but they don't learn anything about other people's payments to you.)

But you can get the same effect another way: just give each payer a unique address. Rather than posting a single public donation address on your website, have a button that generates a new unique address and saves the private key, or selects the next address from a long list of pre-generated addresses (whose private keys you hold somewhere safe). Just as before, the payments all go to separate addresses and there is no way to correlate them, nor for one payer to see that other payments went to you.

So the only difference with stealth addresses is essentially to move the chore of producing a unique address from the server to the client. Indeed, in some ways stealth addresses may be worse, since very few people use them, and if you are known to be one of them, it will be easier to connect stealth transactions with you.

It doesn't provide "100% anonymity". The fundamental anonymity weakness of Bitcoin remains - that everyone can follow the chain of payments, and if you know something about one transaction or the parties to it, you can deduce something about where those coins came from or where they went.
(my italics)

Unfortunately, the client handles this quite poorly, stealth addresses are very much longer than WIF addresses and this wrecks the GUI comprehensively, the label is truncated in the display and the rest of the space is filled with (let's not be too coy about this) random characters of a profoundly uninformative and uncommunicative nature:

e.g.

SfSLMCoinMainNetworkBurnAddr1DeTK5

vs

dooGjSHpy846JJtVcxfCxVoA2o9aaPsC98cJvpRiqrtAAyXwkcUDFEpTFNpppx7ENMHBx6yDrEyhLHX NsdLvwwYbet4pLvtqAbweDB

Unless there are strenuous objections (if so, please communicate them), I intend to revert the addition of stealth addresses to Slimcoin 0.5.0 for the following reasons:

a. the core functionality already exists in the Slimcoin codebase
b. the imported code introduces additional, untested cryptography
c. receipts and payments to stealth addresses are not shown in the GUI
d. there are no tests
e. 102-character addresses overwhelm the GUI's layout algorithms

Cheers

Graham
gavrilo77
Hero Member
*****
Online Online

Activity: 692



View Profile
April 03, 2017, 02:11:16 PM
 #510

I compiled again wallet from master.

1. Sync is OK
2. Mining works (low hash rate not found block yet)
3. Burn works well (burnt 1000 SLM and waiting for block)

BitSend ◢◤Clients | Source
www.bitsend.info
| Your Digital Network | 10MB Blocks
| Algo: XEVAN | DK3 | Masternodes
| BSD - Tether USDT Pair ✔
| Bittrex | C.Gather | S.Exchange
| Cryptopia | LOCALCRYPTO | Livecoin
| CoinPayments | Faucet | Bitsend Airdrop

████
 ████
  ████
   ████
    ████
     ████
      ████
       ████
        ████
       ████
      ████
     ████
    ████
   ████
  ████
 ████
████

████
 ████
  ████
   ████
    ████
     ████
      ████
       ████
        ████
       ████
      ████
     ████
    ████
   ████
  ████
 ████
████
gjhiggins
Legendary
*
Offline Offline

Activity: 1218



View Profile WWW
April 03, 2017, 03:04:26 PM
 #511

Unless there are strenuous objections (if so, please communicate them), I intend to revert the addition of stealth addresses to Slimcoin 0.5.0

In the absence of (promptly notified) strenuous objections, I have effected this reversion.

Tests still pass.

Importantly, this latter fact can be verified by consulting the Travis CI build record:

https://travis-ci.org/gjhiggins/slimcoin-dev/builds/218075235

The Travis CI build uses Ubuntu Trusty (14.04) - both slimcoind and Slimcoin-Qt now compile successfully under Ubuntu 14.04.

I'm still refining this phase of automating the build process, hence the use of an alternative repos.

https://travis-ci.org/slimcoin-project/Slimcoin

Please note, the changes enabling compilation under 14.04 have not yet been propagated to Slimcoin master.

https://github.com/slimcoin-project/Slimcoin/commit/a010f8e1dcf0a893bf75c88671920612d9a4e43c

Note for users of 14.04: due to differences in support for C++ versions, to compile successfully with 14.04, use the following:

qmake RELEASE=1 USE_QRCODE=1 FIRST_CLASS_MESSAGING=1 USE_UPNPC=1 USE_OLDC=1

Cheers

Graham
gavrilo77
Hero Member
*****
Online Online

Activity: 692



View Profile
April 04, 2017, 07:33:41 AM
 #512

Unless there are strenuous objections (if so, please communicate them), I intend to revert the addition of stealth addresses to Slimcoin 0.5.0

In the absence of (promptly notified) strenuous objections, I have effected this reversion.

Tests still pass.

Importantly, this latter fact can be verified by consulting the Travis CI build record:

https://travis-ci.org/gjhiggins/slimcoin-dev/builds/218075235

The Travis CI build uses Ubuntu Trusty (14.04) - both slimcoind and Slimcoin-Qt now compile successfully under Ubuntu 14.04.

I'm still refining this phase of automating the build process, hence the use of an alternative repos.

https://travis-ci.org/slimcoin-project/Slimcoin

Please note, the changes enabling compilation under 14.04 have not yet been propagated to Slimcoin master.

https://github.com/slimcoin-project/Slimcoin/commit/a010f8e1dcf0a893bf75c88671920612d9a4e43c

Note for users of 14.04: due to differences in support for C++ versions, to compile successfully with 14.04, use the following:

qmake RELEASE=1 USE_QRCODE=1 FIRST_CLASS_MESSAGING=1 USE_UPNPC=1 USE_OLDC=1

Cheers

Graham


Wallet compiled successfully in Ubuntu 14.04!!!

Edit: What need more to have final release? Thank you

BitSend ◢◤Clients | Source
www.bitsend.info
| Your Digital Network | 10MB Blocks
| Algo: XEVAN | DK3 | Masternodes
| BSD - Tether USDT Pair ✔
| Bittrex | C.Gather | S.Exchange
| Cryptopia | LOCALCRYPTO | Livecoin
| CoinPayments | Faucet | Bitsend Airdrop

████
 ████
  ████
   ████
    ████
     ████
      ████
       ████
        ████
       ████
      ████
     ████
    ████
   ████
  ████
 ████
████

████
 ████
  ████
   ████
    ████
     ████
      ████
       ████
        ████
       ████
      ████
     ████
    ████
   ████
  ████
 ████
████
gjhiggins
Legendary
*
Offline Offline

Activity: 1218



View Profile WWW
April 04, 2017, 10:34:51 AM
 #513

Wallet compiled successfully in Ubuntu 14.04!!!

phew! that's a relief.

Quote
Edit: What need more to have final release? Thank you

I may have to strip out the torrent stuff. Although it only uses SQlite for local storage, Qt drags in mysqlclient libs (spit), resulting in:

Code:
/usr/lib/mxe/usr/i686-w64-mingw32.static/lib/libcrypto.a(sha256.o):sha256.c:(.text+0x2d0): multiple definition of `SHA224'
/usr/lib/mxe/usr/i686-w64-mingw32.static/lib/libmysqlclient.a(my_sha2.cc.obj):my_sha2.cc:(.text+0x180): first defined here
/usr/lib/mxe/usr/i686-w64-mingw32.static/lib/libcrypto.a(sha256.o):sha256.c:(.text+0x630): multiple definition of `SHA256'
/usr/lib/mxe/usr/i686-w64-mingw32.static/lib/libmysqlclient.a(my_sha2.cc.obj):my_sha2.cc:(.text+0x100): first defined here
/usr/lib/mxe/usr/i686-w64-mingw32.static/lib/libcrypto.a(sha512.o):sha512.c:(.text+0x13f0): multiple definition of `SHA384'
/usr/lib/mxe/usr/i686-w64-mingw32.static/lib/libmysqlclient.a(my_sha2.cc.obj):my_sha2.cc:(.text+0x80): first defined here
/usr/lib/mxe/usr/i686-w64-mingw32.static/lib/libcrypto.a(sha512.o):sha512.c:(.text+0x1cb0): multiple definition of `SHA512'
/usr/lib/mxe/usr/i686-w64-mingw32.static/lib/libmysqlclient.a(my_sha2.cc.obj):my_sha2.cc:(.text+0x0): first defined here
collect2: error: ld returned 1 exit status
Makefile.Release:448: recipe for target 'release/slimcoin-qt.exe' failed

which is a bit of a show-stopper. In MXE, the conjunction of crypto and database in Qt is not exactly a well-trodden path by the looks of it as I can't even find any hints of a reported issue.

I will cast around for different approaches, maybe use a more recent version of MXE, maybe clone the repos and compile a version of MXE without the issue, maybe see if I can find an example that uses BerkeleyDB instead, maybe try the build on 14.04 / 15.10 / 17.04. Maybe not bother with DB storage at all.

Cheers

Graham
gavrilo77
Hero Member
*****
Online Online

Activity: 692



View Profile
April 04, 2017, 12:30:22 PM
 #514

Wallet compiled for Ubuntu 17.04 Beta 2 successful

Edit: Found this for Windows wallet https://github.com/MonetaryUnit/MUE-Src/wiki/Compiling-MUE#todo i will try it later

BitSend ◢◤Clients | Source
www.bitsend.info
| Your Digital Network | 10MB Blocks
| Algo: XEVAN | DK3 | Masternodes
| BSD - Tether USDT Pair ✔
| Bittrex | C.Gather | S.Exchange
| Cryptopia | LOCALCRYPTO | Livecoin
| CoinPayments | Faucet | Bitsend Airdrop

████
 ████
  ████
   ████
    ████
     ████
      ████
       ████
        ████
       ████
      ████
     ████
    ████
   ████
  ████
 ████
████

████
 ████
  ████
   ████
    ████
     ████
      ████
       ████
        ████
       ████
      ████
     ████
    ████
   ████
  ████
 ████
████
gavrilo77
Hero Member
*****
Online Online

Activity: 692



View Profile
April 04, 2017, 07:01:26 PM
 #515

My error trying to compile windows wallet

Code:
/mnt/mxe/usr/bin/i686-w64-mingw32.static-ld: cannot find -lboost_system-mgw49-mt-s-1_55
/mnt/mxe/usr/bin/i686-w64-mingw32.static-ld: cannot find -lboost_filesystem-mgw49-mt-s-1_55
/mnt/mxe/usr/bin/i686-w64-mingw32.static-ld: cannot find -lboost_program_options-mgw49-mt-s-1_55
/mnt/mxe/usr/lib/gcc/i686-w64-mingw32.static/5.4.0/../../../../i686-w64-mingw32.static/lib/../lib/libcrypto.a(sha256.o):sha256.c:(.text+0x2d0): multiple definition of `SHA224'
/mnt/mxe/usr/lib/gcc/i686-w64-mingw32.static/5.4.0/../../../../i686-w64-mingw32.static/lib/../lib/libmysqlclient.a(my_sha2.cc.obj):my_sha2.cc:(.text+0x180): first defined here
/mnt/mxe/usr/lib/gcc/i686-w64-mingw32.static/5.4.0/../../../../i686-w64-mingw32.static/lib/../lib/libcrypto.a(sha256.o):sha256.c:(.text+0x630): multiple definition of `SHA256'
/mnt/mxe/usr/lib/gcc/i686-w64-mingw32.static/5.4.0/../../../../i686-w64-mingw32.static/lib/../lib/libmysqlclient.a(my_sha2.cc.obj):my_sha2.cc:(.text+0x100): first defined here
/mnt/mxe/usr/lib/gcc/i686-w64-mingw32.static/5.4.0/../../../../i686-w64-mingw32.static/lib/../lib/libcrypto.a(sha512.o):sha512.c:(.text+0x13f0): multiple definition of `SHA384'
/mnt/mxe/usr/lib/gcc/i686-w64-mingw32.static/5.4.0/../../../../i686-w64-mingw32.static/lib/../lib/libmysqlclient.a(my_sha2.cc.obj):my_sha2.cc:(.text+0x80): first defined here
/mnt/mxe/usr/lib/gcc/i686-w64-mingw32.static/5.4.0/../../../../i686-w64-mingw32.static/lib/../lib/libcrypto.a(sha512.o):sha512.c:(.text+0x1cb0): multiple definition of `SHA512'
/mnt/mxe/usr/lib/gcc/i686-w64-mingw32.static/5.4.0/../../../../i686-w64-mingw32.static/lib/../lib/libmysqlclient.a(my_sha2.cc.obj):my_sha2.cc:(.text+0x0): first defined here
collect2: error: ld returned 1 exit status
Makefile.Release:442: recipe for target 'release/slimcoin-qt.exe' failed
make: *** [release/slimcoin-qt.exe] Error 1

BitSend ◢◤Clients | Source
www.bitsend.info
| Your Digital Network | 10MB Blocks
| Algo: XEVAN | DK3 | Masternodes
| BSD - Tether USDT Pair ✔
| Bittrex | C.Gather | S.Exchange
| Cryptopia | LOCALCRYPTO | Livecoin
| CoinPayments | Faucet | Bitsend Airdrop

████
 ████
  ████
   ████
    ████
     ████
      ████
       ████
        ████
       ████
      ████
     ████
    ████
   ████
  ████
 ████
████

████
 ████
  ████
   ████
    ████
     ████
      ████
       ████
        ████
       ████
      ████
     ████
    ████
   ████
  ████
 ████
████
d5000
Legendary
*
Offline Offline

Activity: 1582



View Profile
April 05, 2017, 09:08:41 AM
 #516

Unless there are strenuous objections (if so, please communicate them), I intend to revert the addition of stealth addresses to Slimcoin 0.5.0

In the absence of (promptly notified) strenuous objections, I have effected this reversion.

That's OK for me. Thought a bit about it but I think it doesn't make a significant difference.

Quote
Note for users of 14.04: due to differences in support for C++ versions, to compile successfully with 14.04, use the following:

qmake RELEASE=1 USE_QRCODE=1 FIRST_CLASS_MESSAGING=1 USE_UPNPC=1 USE_OLDC=1

Does this also work when compiling the daemon alone? I don't want to install QT on my small cloud vserver Wink

       ▀
   ▄▄▄   ▄▀
   ███ ▄▄▄▄  ██
       ████
    ▄  ▀▀▀▀
▄▄
      ██    ▀▀
██▄█▄▄▄████████
▄▄▄▄▄▄▄▄▀▀███▀▀▀
██████████████████
████▄▀▄▀▄▀███▀▀▀▀▀
████▄▀▄▀▄▀███ ▀
████▄▀▄▀▄▀████████
▀█████████████████
]
,CoinPayments,
█████
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████
█████
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████
█████
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████
gavrilo77
Hero Member
*****
Online Online

Activity: 692



View Profile
April 05, 2017, 09:38:23 AM
 #517

Unless there are strenuous objections (if so, please communicate them), I intend to revert the addition of stealth addresses to Slimcoin 0.5.0

In the absence of (promptly notified) strenuous objections, I have effected this reversion.

That's OK for me. Thought a bit about it but I think it doesn't make a significant difference.

Quote
Note for users of 14.04: due to differences in support for C++ versions, to compile successfully with 14.04, use the following:

qmake RELEASE=1 USE_QRCODE=1 FIRST_CLASS_MESSAGING=1 USE_UPNPC=1 USE_OLDC=1

Does this also work when compiling the daemon alone? I don't want to install QT on my small cloud vserver Wink

slimcoind is fine as well i was using make -f makefile.unix USE_UPNP=-

BitSend ◢◤Clients | Source
www.bitsend.info
| Your Digital Network | 10MB Blocks
| Algo: XEVAN | DK3 | Masternodes
| BSD - Tether USDT Pair ✔
| Bittrex | C.Gather | S.Exchange
| Cryptopia | LOCALCRYPTO | Livecoin
| CoinPayments | Faucet | Bitsend Airdrop

████
 ████
  ████
   ████
    ████
     ████
      ████
       ████
        ████
       ████
      ████
     ████
    ████
   ████
  ████
 ████
████

████
 ████
  ████
   ████
    ████
     ████
      ████
       ████
        ████
       ████
      ████
     ████
    ████
   ████
  ████
 ████
████
gjhiggins
Legendary
*
Offline Offline

Activity: 1218



View Profile WWW
April 05, 2017, 01:41:55 PM
 #518

Unless there are strenuous objections (if so, please communicate them), I intend to revert the addition of stealth addresses to Slimcoin 0.5.0
In the absence of (promptly notified) strenuous objections, I have effected this reversion.
That's OK for me. Thought a bit about it but I think it doesn't make a significant difference.
Quote
Note for users of 14.04: due to differences in support for C++ versions, to compile successfully with 14.04, use the following:
qmake RELEASE=1 USE_QRCODE=1 FIRST_CLASS_MESSAGING=1 USE_UPNPC=1 USE_OLDC=1
Does this also work when compiling the daemon alone? I don't want to install QT on my small cloud vserver Wink

When compiling the daemon, just use the standard make -f makefile.unix

 The Travis CI log shows all the commands executed and the results - the slimcoind binary is compiled first, then (atm) the test_slimcoin is compiled and run, then finally the Qt wallet is compiled.

Cheers

Graham

Edited for brevity
d5000
Legendary
*
Offline Offline

Activity: 1582



View Profile
April 08, 2017, 06:40:27 AM
 #519

When compiling the daemon, just use the standard make -f makefile.unix

Thanks! The compilation works now with Boost 1.54. Unfortunately, the daemon still crashes (segfaults) about ~10 minutes after startup (as before, last sign of life in debug log is the "CBlock" line). I will test the newest code now on my other machine.

Just a small question about the version numbering: Am I right that the "prerelease" branch would be the "stable" 0.4 version and the master branch is meant to be 0.5? Or are both 0.5? It's because I plan to update the OP a bit with the newest developments.

       ▀
   ▄▄▄   ▄▀
   ███ ▄▄▄▄  ██
       ████
    ▄  ▀▀▀▀
▄▄
      ██    ▀▀
██▄█▄▄▄████████
▄▄▄▄▄▄▄▄▀▀███▀▀▀
██████████████████
████▄▀▄▀▄▀███▀▀▀▀▀
████▄▀▄▀▄▀███ ▀
████▄▀▄▀▄▀████████
▀█████████████████
]
,CoinPayments,
█████
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████
█████
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████
█████
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████
gjhiggins
Legendary
*
Offline Offline

Activity: 1218



View Profile WWW
April 08, 2017, 11:34:16 AM
 #520

When compiling the daemon, just use the standard make -f makefile.unix

Thanks! The compilation works now with Boost 1.54. Unfortunately, the daemon still crashes (segfaults) about ~10 minutes after startup (as before, last sign of life in debug log is the "CBlock" line). I will test the newest code now on my other machine.

That's clearly unsatisfactory, I shall investigate further. AIUI, this is on Ubuntu Trusty? Is that on a 32-bit or 64-bit architecture? (I seem to have acquired two “Trusty” VMs, one for a 64 bit arch, one for a 32-bit but I have little idea whether the difference has any effect unless the actual machine on which I'm running it is 32-bit).

Quote
Just a small question about the version numbering: Am I right that the "prerelease" branch would be the "stable" 0.4 version and the master branch is meant to be 0.5? Or are both 0.5? It's because I plan to update the OP a bit with the newest developments.

Now that the dust is beginning to settle on the codebase, we can switch the default github repos back to "master" and use the 0.5 tag to distinguish the supported Linux “0.5 release” build and use the release page to offer downloadable 0.5 binaries for Windows and OS X. Then we can return to the standard “developers work in their own branch” approach. The current “slimcoin” branch can simply be renamed to “slimcoin 0.4”.

As far as I can figure out from reading the source code, the release version advertised by the running app is taken from the last git tag (which explains why changing the version number in version.h seems to have no effect).

Locally, I could tag my clone as 0.6.6.6, compile the app and the running app would report 0.6.6.6. If I were to push that tag to the public repos, all subsequently cloned+compiled apps would advertise themselves as 0.6.6.6.

There's a 6th-level git wizard's spell of push-release-tag-to-public-repos to be uttered at some point (RTFM, Graham). After this, the GitHub repos “release” page can then be loaded with the (correctly-functioning) platform-specific binaries of Slimcoin 0.5 for Windows and OS X.

Organic life-forms are advised not to try this with Linux binaries because, basically, there's only one supported latest version of Windows and OS X and therefore static libs are reliable on those platforms whereas that is not the case with Linux where dynamic libraries are the norm (AIUI). I could offer Linux builds that link against dynamic system  libraries but I'm not in a position to offer support for local deployment on arbitrary Linux systems with arbitrarily-different dynamic libs.

What I can offer is a standalone deployment script using Vagrant (for an optional VM-based build) and ansible provisioning. Ansible is a Python+YAML devops tool which scripts the d/l+compile sequence to either localhost or a Vagrant VM using standard apt-get install to provision the host appropriately to the specific Linux distro and version (g++, Qt, openssl, miniupnpc, qrencode, etc).

Even if folks don't want to go as far as a VM build, the Ansible “playbook” spells out each step in excruciating detail, f'rinstance this stanza is from the companion MXE-compile-Slimcoin playbook (step-by-step cross-compile build from source on a VM for increased peace-of-mind) that retrieves Qt sources, nukes the mysql references and compiles:

Code:
---
  - name: remove mysqllib from Qt5 compilation
    action:  shell cd /mnt/mxe; grep -v -- '-mysql' src/qtbase.mk | sed -e 's/libmysqlclient //' > /tmp/foo; mv /tmp/foo src/qtbase.mk;

  - name: compile Qt5
    action:  shell cd /mnt/mxe; make MXE_TARGETS="i686-w64-mingw32.static" qttools
    register: qtreport
  - debug:
      msg: '{{ qtreport }}'

This is just an illustrative example in which I tested my hypothesis that the mysql references could be relatively trivially removed from the standard MXE cross-compile build were it to prove desirable.

(And yup, it did run all the way through and created a Windows binary from freshly-compiled libs but I admit to not having the patience to wait for the emulated binary to read the blockchain+index. Perhaps I'll let it play out sometime over the w/e while Ngaio and I are enjoying re-watching John Carpenter's much-overlooked 1974 directorial debut film Dark Star, recently re-posted to youtube in good-quality form.)


Cheers

Graham
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 [26] 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 ... 92 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!