Bitcoin Forum
October 17, 2017, 03:45:23 PM *
News: Latest stable version of Bitcoin Core: 0.15.0.1  [Torrent]. (New!)
 
   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 »
  Print  
Author Topic: Slimcoin | First Proof of Burn currency | Test v0.5  (Read 74231 times)
d5000
Legendary
*
Offline Offline

Activity: 1526


Enjin Coin - Smart Cryptocurrency for Gaming.


View Profile
April 08, 2017, 05:54:51 PM
 #521

AIUI, this is on Ubuntu Trusty? Is that on a 32-bit or 64-bit architecture?

The VPS has Ubuntu Trusty 32-bit. I just compiled the latest master code (g9d111bc9) on my other machine with a newer 64-bit Linux (PCLinuxOS, a rolling release distribution) and there the crash (until now) does not occur and it seems to sync well. Maybe the VPS (32-bit) crash is also related to my VPS being low-end (512 MB RAM + 1,5 GB swap) but it worked reasonably well with earlier Slimcoin versions of the 0.3 and 0.4 branches (except the sync problems I mentioned earlier).

Quote
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”.

Sounds good for me.

I'm not familiar with Vagrant and Ansible but the features you mention look good too. I'll try to take a look at it.

Thank you for your work!

PS: Dark Star made me curious, will see if I can get a version with spanish or german subtitles Wink

1508255123
Hero Member
*
Offline Offline

Posts: 1508255123

View Profile Personal Message (Offline)

Ignore
1508255123
Reply with quote  #2

1508255123
Report to moderator
1508255123
Hero Member
*
Offline Offline

Posts: 1508255123

View Profile Personal Message (Offline)

Ignore
1508255123
Reply with quote  #2

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

Posts: 1508255123

View Profile Personal Message (Offline)

Ignore
1508255123
Reply with quote  #2

1508255123
Report to moderator
1508255123
Hero Member
*
Offline Offline

Posts: 1508255123

View Profile Personal Message (Offline)

Ignore
1508255123
Reply with quote  #2

1508255123
Report to moderator
1508255123
Hero Member
*
Offline Offline

Posts: 1508255123

View Profile Personal Message (Offline)

Ignore
1508255123
Reply with quote  #2

1508255123
Report to moderator
resor
Newbie
*
Offline Offline

Activity: 14


View Profile
April 10, 2017, 08:52:06 AM
 #522

after download the  blockchain, posted by Graham https://minkiz.co/noodlings/slm/slm-datadir-blockfiles.zip , where i need to put the files?
gjhiggins
Legendary
*
Offline Offline

Activity: 1162



View Profile WWW
April 10, 2017, 01:08:33 PM
 #523

after download the  blockchain, posted by Graham https://minkiz.co/noodlings/slm/slm-datadir-blockfiles.zip , where i need to put the files?

The intended location for the block files in slm-datadir-blockfiles.zip is wherever datadir is configured to be.

datadir is the (individually-configurable) location of the standard set of data files and sub-directories that are automatically created when the app is first run i.e. peers.dat, wallet.dat, debug.log, blk00001.dat,  database/, etc.

(The command-line option -datadir=<dir> is how a non-default location for the data files is specified: https://en.bitcoin.it/wiki/Running_Bitcoin)

By default, datadir is located in the user's home directory (commonly aliased as HOME or ~).

The default datadir values are hard-coded - https://github.com/slimcoin-project/Slimcoin/blob/master/src/util.cpp#L861
Code:
   // Windows: C:\Documents and Settings\username\Application Data\SLIMCoin
    // Mac: ~/Library/Application Support/SLIMCoin
    // Unix: ~/.slimcoin

The content of the zip archive is reported as:
Code:
gjh@ashpool:~/.slimcoin$ unzip -l slm-datadir-blockfiles.zip
Archive:  slm-datadir-blockfiles.zip
  Length      Date    Time    Name
---------  ---------- -----   ----
510494780  2017-03-28 01:17   blk0001.dat
611368960  2017-03-28 01:17   blkindex.dat
        0  2017-03-28 01:07   database/
 10485759  2017-03-28 01:17   database/log.0000010055
---------                     -------
1132349499                     4 files

(Yes, sorry, 28th March is correct. I did set up a scheduled task to refresh it daily but it just fails and I haven't yet figured out why).

Finally, the answer:

Copy slm-datadir-blockfiles.zip to your datadir and unzip the archive in place, i.e. the contents will be written to datadir.

(In due course, when I've learned to pronounce correctly the spell of create-slimcoin-readable-bootstrap.dat, I will publish a bootstrap.dat at reasonably frequent intervals but until then, all I can manage is a stammered “cd ~/.slimcoin; zip -r slm-datadir-blockfiles.zip blk* database” which is rather crude but at least it's known to work on Linux and OS X platforms.)

Cheers

Graham
PeterTheGrape
Sr. Member
****
Offline Offline

Activity: 252


View Profile
April 10, 2017, 04:41:33 PM
 #524

For a coin with so many heavy hitters this seems ignored. But also unobtainable for a person who does not mine? No exchanges?
psycodad
Hero Member
*****
Offline Offline

Activity: 543



View Profile
April 10, 2017, 05:21:04 PM
 #525

For a coin with so many heavy hitters this seems ignored. But also unobtainable for a person who does not mine? No exchanges?

It is traded on Novaexchange: https://novaexchange.com/market/BTC_SLM/

Though you can still easily mine a few coins from within the wallet and the increase your holdings by burning and staking.

HTH

Protestatio facto contraria non valet.
resor
Newbie
*
Offline Offline

Activity: 14


View Profile
April 10, 2017, 10:41:37 PM
 #526

after i put the content of slm-datadir-blockfiles.zip in datadir , i cant check wallet or do something , it says: "blockchain download required" , there is a way to fix it?
cryptovore
Member
**
Offline Offline

Activity: 97


View Profile
April 11, 2017, 05:42:09 AM
 #527

It means the blockchain wasn't downloaded or it's in a different location than the one expected. Have a look again at the explanation of Graham above and try to follow closely those steps.
Warren.Buffet
Full Member
***
Offline Offline

Activity: 125


View Profile
April 11, 2017, 05:49:38 AM
 #528

For a coin with so many heavy hitters this seems ignored. But also unobtainable for a person who does not mine? No exchanges?

It is traded on Novaexchange: https://novaexchange.com/market/BTC_SLM/

Though you can still easily mine a few coins from within the wallet and the increase your holdings by burning and staking.

HTH

Is the original dev still involved?
gjhiggins
Legendary
*
Offline Offline

Activity: 1162



View Profile WWW
April 11, 2017, 02:28:53 PM
 #529

after i put the content of slm-datadir-blockfiles.zip in datadir , i cant check wallet or do something , it says: "blockchain download required" , there is a way to fix it?

Blockfiles created by a Linux-hosted client may not work for a Windows-hosted client. At worst, shut down the client, delete everything in datadir (except wallet.dat, ofc) and then re-start the client - it should synch from the network.

Other than that, somewhere in the previous posts around Dec/Jan there was a Windows blockchain dump for Slimcoin made available which should cut down the syncing time. I hope you'll forgive me for not providing a precise reference, Real Life(tm) is calling.

Cheers

Graham
resor
Newbie
*
Offline Offline

Activity: 14


View Profile
April 11, 2017, 07:42:43 PM
 #530

after i put the content of slm-datadir-blockfiles.zip in datadir , i cant check wallet or do something , it says: "blockchain download required" , there is a way to fix it?

Blockfiles created by a Linux-hosted client may not work for a Windows-hosted client. At worst, shut down the client, delete everything in datadir (except wallet.dat, ofc) and then re-start the client - it should synch from the network.

Other than that, somewhere in the previous posts around Dec/Jan there was a Windows blockchain dump for Slimcoin made available which should cut down the syncing time. I hope you'll forgive me for not providing a precise reference, Real Life(tm) is calling.

Cheers

Graham



Im using ubuntu 16.04 , not windows
ArchitektoR
Full Member
***
Offline Offline

Activity: 121


View Profile
April 14, 2017, 01:43:20 PM
 #531

Debian 8 x64 - still crashing with:

Code:
from src/bitcoinrpc.cpp:8:
src/bignum.h:52:24: error: invalid use of incomplete type ?BIGNUM {aka struct bignum_st}?
 class CBigNum : public BIGNUM
gjhiggins
Legendary
*
Offline Offline

Activity: 1162



View Profile WWW
April 14, 2017, 02:55:23 PM
 #532

Debian 8 x64 - still crashing with:

Code:
from src/bitcoinrpc.cpp:8:
src/bignum.h:52:24: error: invalid use of incomplete type ?BIGNUM {aka struct bignum_st}?
 class CBigNum : public BIGNUM

Known bug with Debian 8 apparently: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855574

Cheers

Graham
ArchitektoR
Full Member
***
Offline Offline

Activity: 121


View Profile
April 14, 2017, 03:17:36 PM
 #533


yes, googled this too - but no solution suggested.. will try to build on Ubuntu VM and move to Debian
gjhiggins
Legendary
*
Offline Offline

Activity: 1162



View Profile WWW
April 14, 2017, 06:37:44 PM
 #534


yes, googled this too - but no solution suggested.. will try to build on Ubuntu VM and move to Debian

You may not need to go down that route. Fortunately, I am unable to replicate the issue. I have a Vagrant VM of Jessie on which Slimcoin master compiles, the GUI executes and all tests pass.

I can't give you chapter and verse just yet. I was working on a Vagrant+ansible Jessie deployment but abandoned it, upgrading to the desktop for convenience - that's where I built the Jessie binaries.

I'll update the repos: https://github.com/gjhiggins/ansible-slm-jessie with a known-to-work version.

Cheers

Graham
gjhiggins
Legendary
*
Offline Offline

Activity: 1162



View Profile WWW
April 15, 2017, 12:29:05 AM
 #535

I'll update the repos: https://github.com/gjhiggins/ansible-slm-jessie with a known-to-work version.

Now known to work reliably, chapter and verse on building for Debian Jessie Vagrant VM.

Cheers

Graham
cryptovore
Member
**
Offline Offline

Activity: 97


View Profile
April 15, 2017, 11:37:41 AM
 #536

Successfully compiled and running a Mac OS GUI.  Now let's play with the OP_RETURN thingie...
gjhiggins
Legendary
*
Offline Offline

Activity: 1162



View Profile WWW
April 16, 2017, 12:08:48 PM
 #537

Successfully compiled and running a Mac OS GUI.  Now let's play with the OP_RETURN thingie...

Good to know, thanks.

Background reading: Bartoletti and Pompianu's paper (reporting Feb '17 results) “An analysis of Bitcoin OP RETURN metadata. Massimo Bartoletti and Livio Pompianu, Universit`a degli Studi di Cagliari, Cagliari, Italy” (PDF), presented at Financial Cryptography and Data Security April 2017.

Latest commit:

https://github.com/slimcoin-project/Slimcoin/commit/05ee8c0a879afa3263a1b348a94e8a98e87206db - “Show OP_RETURN message in transaction details”



Note, cost of creating an OP_RETURN tx has doubled (from 0.01 SLM to 0.02 SLM) - it transpires that 0-valued tx are prohibited as a hard-coded element of the consensus mechanism

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

Code:
if ((!txout.IsEmpty()) && txout.nValue < MIN_TXOUT_AMOUNT)
    return DoS(100, error("CTransaction::CheckTransaction() : txout.nValue below minimum"));

Changing this to allow 0-valued tx would create a ... <dramatically-clashing-chord/> hard fork. Old clients would be peremptorily excluded from any new, 0-valued-tx-tolerant consensus and that would be a bummer.

So instead, I adjusted the OP_RETURN tx generation code to add a 0.01 CENT value to the tx, which enables it to be accepted as a valid tx by legacy 0.3/0.4 clients as well as the 0.5 johnny-come-latelys.

NOTE: TESTNET ONLY PLEASE I've removed the “enforced testnet mode” from the code, so there's every opportunity to be a good Slimcitizen and use -testnet when experimenting. I create a copy of ~/.slimcoin/slimcoin.conf as ~/.slimcoin/slimcoin_testnet.conf and reference that specifically on the command line: ./slimcoin-qt -testnet -conf=slimcoin_testnet.conf. It has an elevated reservebalance level and a blocknotify script specialised to testnet.

Testnet seed node (1 thread devoted to mining just to keep the blockchain ticking over): addnode=144.76.64.49:41684, PM me for testnet coins.


Cheers

Graham

Edit: addeddaddnodde
gjhiggins
Legendary
*
Offline Offline

Activity: 1162



View Profile WWW
April 16, 2017, 04:12:22 PM
 #538

It has an elevated reservebalance level and a blocknotify script specialised to testnet.

“What blocknotify script?” asks a hypothetical discourse device. Well, the client can be configured to execute a specified program whenever the client receives a new block.

In my slimcoin_testnet.conf it is configured as a shell script:
Code:
blocknotify=/opt/slm/scripts/slm-testnet-blocknotify.sh %s

when executed, the %s gets replaced by the actual block hash, bound in the shell environment to $@.

The shell script:
Code:
#!/bin/sh
BLOCKHASH="$@" /usr/bin/python3.5 /opt/slm/scripts/slm-testnet-blocknotify.py  > /tmp/blocknotify.log 2>&1
echo "${@}" >> /tmp/blocknotify.log

which, in turn, runs a Python script that picks up the block hash from the environment, performs a series of RPC calls on the client, starting with getblock <BLOCKHASH>, converting the returned JSON statements into RDF statements and working its way through the pointers finally to create an complete RDF graph representation of the block, its transactions, their values and the addresses involved. It records around three dozen facts about each block.

(~950000 blocks * 36 triples = 34,200,000 triples, so an RDF graph of mainnet will a) take time to generate and b) have to be maintained in separate chunks. Fortunately SPARQL can run “federated” queries, i.e. treat the separate chunks as one for querying porpoises.)

The RDF is then posted to an instance of the Apache Jena Fuseki SPARQL server running on the (same) machine which then offers SPARQL querying of a contemporaneous RDF graph of the blockchain.

The following image shows a SPARQL query that lists all distinct OP_RETURN tx messages on the testnet blockchain:



(The SPARQL endpoint shown in the image is active and accessible)

That's all she wrote, literally.  If we want to provide more information about a particular inscription, such as a description of the nature of the content of the torrent identified by the inscribed torrent hash, then for us it has to be off-chain.

Off-chain data storage is often implemented by creating additional data tables in the -datadir. Unfortunately, this approach also adds significantly to the maintenance load and this directly translates into a significant increase in the cost of ownership for the already woefully under-supported user. Let’s be realistic, people aren't exactly queuing up to shoulder the load of curating the content that they create in the course of their netsocializing, they much prefer it to be someone else's problem even at the price of a significant concession of privacy.

The real show-stopper is that the locally-stored data isn't broadcast across the peer-to-peer network, it remains locally siloed and thus useful to neither man nor beast.

A more plausible approach would be to engineer a reliable external social consensus using an RDF graph representation of the blockchain for provable veracity. The RDF representation is both public and accessible so it's trivial to establish whether or not it's a correct mapping from the acyclic directed blockchain graph to the acyclic directed RDF graph.

Given that the RDF graph is a one-to-one symbolic correspondence to the blockchain, referring to :C0000000733567067927d0778bdee1ad3034ecc60e49cfc3ae05dbc3a1eddbb60 will get you the recorded metadata for that block:


:C0000000733567067927d0778bdee1ad3034ecc60e49cfc3ae05dbc3a1eddbb60 a :Block ;
    :difficulty 0.06464541 ;
    :flags "proof-of-work"^^xsd:string ;
    :height 759 ;
    :mint 6.19 ;
    :previousblockhash :C8fe77bb34c5aec9206a3c73beccaf1fc53e6d4afe297c3782f57c09e4eb9c627 ;
    :size 355 ;
    :time 1492346152 .


The absence of a statement about the nextblock defines this as the last block in the chain at the time recorded.

So, given that the query:

SELECT ?subject
WHERE {
  ?subject rdf:type <http://purl.org/net/bel-epa/ccy#TransactionOutput> .
  ?subject <http://purl.org/net/bel-epa/ccy#inscription> "magnet:?xt=urn:btih:e940a7a57294e4c98f62514b32611e38181b6cae"
}


yields a reference to the TxO <http://purl.org/net/bel-epa/ccy#C1887d7380f770c99c0f9d08c38b7f01d71913b2ce791d1771ddfcfddda69f49d-O-2>

I can make further statements, using the retrieved TxO reference as an identifier and using expressions drawn from familiar vocabularies (in this instance, for clarity I'm using just the Dublin Core metadata elements):

:gjh-00000001 a :Inscription ;
  :inscription  "magnet:?xt=urn:btih:e940a7a57294e4c98f62514b32611e38181b6cae"^^xsd.string ;
  dc:title "Arch Linux 2013.01.04 (www.archlinux.org)"^^xsd.string ;
  dc:date 2013-01-04T22:09:20Z ;
  dc:identifier http://purl.org/net/bel-epa/ccy#C1887d7380f770c99c0f9d08c38b7f01d71913b2ce791d1771ddfcfddda69f49d-O-2 ;
  dc.source: "magnet:?xt=urn:btih:c8cde7428b44142b04d88b91785ecf0f20d16903&dn=archlinux-2013.02.01-x86_64.iso&tr=udp://tracker.archlinux.org:6969&tr=http://tracker.archlinux.org:6969/announce" ;
  dc:description "kernel_version 3.6.11"^^xsd.string .


I can add that to my local graph, dump it on pastebin or, one day in the dim and distant future, I could even publish it to a group-maintained community-serving RDF graph running on several DO/AWS instances so that other users can choose to add to their whitelisted resources.


Cheers

Graham
resor
Newbie
*
Offline Offline

Activity: 14


View Profile
April 17, 2017, 08:06:31 PM
 #539

Hello  , srry for bothering all the time , but im very interested in mining this   coin , my problem is that when  i  put the chain block data into the  dir it saays the error : "blockchain download required".
It means that i need to download the chain block with the slimcoind program?... how ?
gjhiggins
Legendary
*
Offline Offline

Activity: 1162



View Profile WWW
April 18, 2017, 11:28:44 PM
 #540

Pre-release binaries of current master for checking out on testnet for anyone who wants 'em:

https://minkiz.co/noodlings/slm/SLIMCoin-Qt-v05-BSD4.8.dmg
https://minkiz.co/noodlings/slm/slimcoin-qt-05-win-prerelease.zip
https://minkiz.co/noodlings/slm/slimcoin-0.5-xenial.zip

QtCreator produced a 100Mb slimcoin-qt Linux binary via the “Release” build option. It might work on another Xenial installation.

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 »
  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!