Slimcoin | First Proof of Burn currency | Decentralized Web

[gavrilo77]

Pool is not working?

[muf18]

Barry isn't responding to me...

[psycodad]

Guys !!!

Nova started again to accept deposit 

K.

Unfortunately deposits on Novaexchange have been disabled again shortly after...
I wonder how long it takes for them to become fully operational again, it's now more than half a year that they are in almost-closed-down mode..

[bobitza202]

Guys !!!

Nova started again to accept deposit  

K.

Unfortunately deposits on Novaexchange have been disabled again shortly after...
I wonder how long it takes for them to become fully operational again, it's now more than half a year that they are in almost-closed-down mode..

I think they were probably testing or something 

[muf18]

Yeah, but we were at top5-6 in novaexchange, when deposits were open.
Better than anything.
I'm still in the talks with Blockbid (hopefully), GBCAX, and Octaex (0.1BTC, or 1500 votes on exchange).

I was alone at it, so anybody have more propositions?

[d5000]

I'm currently working on the "inscriber" tool I mentioned in my last post (a tool to publish a torrent hash easily from a specific address). Its first alpha is almost ready, but I'm struggling a bit with the raw transaction structure.

Unfortunately, Slimcoin's createrawtransaction command seems to not understand (as far as I didn't something wrong) still the "data" field of the "outputs" dictionary (see here, I think it was added in a newer Bitcoin version), so one must encode the transaction data manually. I've already created the OP_RETURN transactions as a JSON structure, but unfortunately there is no encoderawtransaction feature .

I just saw however, that I'll probably be able to solve that challenge with Graham's excellent article about the genesis block anatomy. It seems to include the structure of a transaction in the second part. Maybe we can publish the transaction structure in the (almost not-used) wiki, too.

BTW: @muf18 - to keep the website up to date: Was Slimcoin added finally at an exchange other than Nova and Freiexchange? Coinsmarket and Coinhouse seem to be both non-operational or outright scams, is this right?

[keliokan]

Guys !!!

Nova started again to accept deposit  

K.

Unfortunately deposits on Novaexchange have been disabled again shortly after...
I wonder how long it takes for them to become fully operational again, it's now more than half a year that they are in almost-closed-down mode..

I think they were probably testing or something 

yes, apparently they just do some scan time to time.
Waiting for the real re-opening !!

K.

[eddycurrent]

Hello all,

Just an interesting article I saw this morning about "burning" bitcoin cash to raise its value:
https://www.smh.com.au/business/investments/burning-coins-how-bitcoin-cash-became-the-world-s-hottest-cryptocurrency-20180424-p4zb9w.html
This tells me that there might be more interest Slimcoin's burn feature if people knew about it.

Regards

[quynhle10t]

Is there a way to keep memory requirements low, by configuration option?

I like to fire up a node on a small VPS with only 512MB Ram..

[muf18]

Barry has made great pool

http://slimcoin.bazco.in

Donate him, for his hard & great work.

BTC:
17evPVkeVJ3H4yPEMpQ6rjyCFEC7FQpb9r

I'll send some too.

[d5000]

Is there a way to keep memory requirements low, by configuration option?

I like to fire up a node on a small VPS with only 512MB Ram..

I did this a couple of months ago (I ran a client on a VPS with 512 MB). It works for Proof of Burn minting if you use a large swap file (1 GB minimum), set the reservebalance so high the client never "stakes", and you should also observe it a bit because it sometimes crashes. However, now I've changed my client to a 1 GB RAM VPS (there are some starting with 2-3 USD per month, even accepting Bitcoin) and it works significantly better (in fact, it never crashed).

If you want to stake, I recommend at least 2 GB RAM plus swap (it works pretty fine on 4 GB RAM but I don't run my "staking client" 24/7).

[gavrilo77]

Seems pool it is not finding blocks?

[keliokan]

Seems pool it is not finding blocks?

My miner does not work on this pool (works perfectly in solo).
crazy hashrate (27 000 khash ?) and all rejected.

K.

[muf18]

I messaged about this issue, I think as he said, it's problem with too low diff adjusted in the pool.

[d5000]

I updated the OP of this thread to include the pool and to inform about some other current developments

The "inscriber" tool I wrote about these days is now completed and being tested on testnet. As it's a "dangerous" tool to use in mainnet (if going havoc it could thrash all your coins, as it creates raw transactions), I'll publish it after some more testing. Even then, caution is necessary - never use it with your main wallet.

As a "side-effect" I learned about Slimcoin's raw transaction format. I have written a little article about it in the Wiki on Github:

https://github.com/slimcoin-project/Slimcoin/wiki/Transaction-Format

It is similar, but not absolutely equal to Bitcoin's old transaction format.

[Sam123]

I updated the OP of this thread to include the pool and to inform about some other current developments

The "inscriber" tool I wrote about these days is now completed and being tested on testnet. As it's a "dangerous" tool to use in mainnet (if going havoc it could thrash all your coins, as it creates raw transactions), I'll publish it after some more testing. Even then, caution is necessary - never use it with your main wallet.

As a "side-effect" I learned about Slimcoin's raw transaction format. I have written a little article about it in the Wiki on Github:

https://github.com/slimcoin-project/Slimcoin/wiki/Transaction-Format

It is similar, but not absolutely equal to Bitcoin's old transaction format.

d5000,
Thanks for the update and having the time to write the article on wiki.
I believe this project also is very good and hopefully soon more community member will join this project.
 

[barrysty1e]

Seems pool it is not finding blocks?

The problem that the pool is having is due to Slimcoin's custom transaction format (as mentioned by d5000).
The pool will correctly identify a blockheader with the correct amount of work, however when it sends this to the daemon using submitblock (along with the transaction data) the daemon then segfaults, as although the dcrypt hash matches - the block contents aren't correct.

The issue was encountered years ago with no proposed solution (https://bitcointalk.org/index.php?topic=613213.3995;wap).

I've worked with another currency 'Cryptonite' that an identical issue, where the solution was to only submit the blockheader (no tx data) using 'getwork'. The reason this works, is the daemon already knows about the transactions it has received via p2p (and its own coinbasetxn for the potential block) - the calculated merkleroot then matches the merkleroot provided in the blockheader.

It's not quite 'getwork over stratum', as its only used for the solution, not the work propagation.

My miner does not work on this pool (works perfectly in solo).
crazy hashrate (27 000 khash ?) and all rejected.

I recently came across the GPU solo-mining code (not the stratum gpu miner @ https://github.com/JonnyLatte/slimminerGPU); this will not work against the pool due to differences in getwork/stratum work format and byteswapping of the nonces (and several other fields).

Even when the daemon had died, while the stratum was still up; it will still return valid hashes as it keeps the last blocktemplate in memory.
More than happy to do some testing if you like.

anyway

I'm writing a small patch to allow the block to be submitted using getwork; will post back on my results in an hour.

james

[keliokan]

Actually i had the same problem using CPU mining.
I'm going to check which version of minerd i used..

K.

My miner does not work on this pool (works perfectly in solo).
crazy hashrate (27 000 khash ?) and all rejected.

I recently came across the GPU solo-mining code (not the stratum gpu miner @ https://github.com/JonnyLatte/slimminerGPU); this will not work against the pool due to differences in getwork/stratum work format and byteswapping of the nonces (and several other fields).

Even when the daemon had died, while the stratum was still up; it will still return valid hashes as it keeps the last blocktemplate in memory.
More than happy to do some testing if you like.

anyway

I'm writing a small patch to allow the block to be submitted using getwork; will post back on my results in an hour.

james

[bobitza202]

Still waiting for nova to open the deposits  

Also, we're seeing an unprecedented market share spread, most probably in the next 2-3 years the majority of share will be held by a group of altcoins, spreaded between 15-20%, with Bitcoin on a lower position, but still in the top 10.

[d5000]

Inscriber tool for easy Slimweb inscriptions

I've tested the inscriber tool in mainnet and now after a few fixes it seems to work OK.

It can be downloaded here: https://github.com/d5000/acme-minitools (download the whole repository).

It uses the blocknotifybase script as a dependency; this is not ideal, but it was the easiest way to realize it In the future it should work as a standalone tool and use the standard configuration file (slimcoin.conf) for the needed parameters.

What does this tool do?

The inscriber tool provides an easy way to inscribe data on the blockchain via OP_RETURN transactions and gives you the ability to control the address from which the inscription is done.

This is important if you want to publish "Slimweb" websites and update them regularly, because in this case an address is the "identifier" of the website. As the current client doesn't allow coin control, currently you need to use workarounds.

NOTE: The Inscriber tool uses the Raw Transactions API. It is therefore a potentially dangerous tool. You should NEVER use it with your main wallet - in theory, a bug could "thrash" your coins. Try it out on testnet and then create a wallet with few coins to create inscriptions. As inscriptions cost only 0.02 SLM, with a few coins you'll be fine for a long time.

Basic Syntax

Code:

python3 inscriber.py INSCRIPTION [ADDRESS] 

INSCRIPTION being the data you want to inscribe (e.g. a magnet link or torrent hash)
ADDRESS being the address (it must be one of your wallet addresses and contain more than 0.02 SLM) from which you want to send the data inscription.


If you don't provide an address, you can select one from the available addresses in your wallet with at least one unspent output of more than 0.02 SLM.

The inscriber tool will select an output from your address and then do the inscription. It can use the "smalldata" format which is recognized by the client as a "message" (default) or the raw OP_RETURN format which provides 4 bytes more. Maximum length is 80 bytes in raw format and 76 bytes in Smalldata format.

Each inscription costs two fees:
- 0.01 minimum standard transaction fee
- 0.01 additional fee because each output must have at least an amount of 0.01 SLM. This fee is burnt, too. (In theory, it could be transferred to another address you own, but you won't be able to use that output normally unless the 0.01 minimum fee is lowered.)

The default behaviour is that the change coins are returned to the original address. If you want to transfer the change to a new address use the "-n" option.

Example transaction created by the Inscriber tool

(More documentation - e.g. a simple howto to create and update a Slimweb site - to follow on the Wiki.)