Topic: Slimcoin | First Proof of Burn currency | Decentralized Web - page 108. (Read 137154 times)

Thanks for new background and your work indeed!
About sim - I dont if it's true, but there were some scam accusation
https://bitcointalksearch.org/topic/--929611
it's little strange.

I'm working on the website Russian translation and I thought you might want to update the banner.

In Sim defense. Dev is active on Slack. Coin price during these years was same or significantly lower than ICO price and everyone had (and still has) equal chances to get coins. Also he gathered only 143 BTC three years ago, so it's old school good type of ICO unlike modern days vaporware ICOs. Slimcoin exchange kinda dead too. At least was before that Reddit post. It only mean people don't want to sell that low. Since Sim isn't yet released it can't be traded on exchanges other than its own.

Yeah I know Simcoin, and it's quite interesting project with some exiciting goals , but:
- development isn't anywhere available, what is doing dev
- most of the materials and prototypes or preview of technology are 3 years old
- there was IPO/ICO
- in reality we don't know if dev is still working on this or just sometime post something, thread is almost dead
- exchange is dead, there isn't any movement - and API/interface is written really amateur at least from my perspective

Slimcoin Project is quite different - we have communication quite frequently with our dev, we have (at least now) quite frequently responses (at least 1 in the day), and we are on rel exchange (nova is small, but at least in most of the parts honest exchange).
And there wasn't premine or ICO.

Interesting that there's another coin with similar name - Simcoin and its dev is saying same things. He's been working on it pretty silently for over 3 years now I think. He also doesn't want wrong people around until the core team and tech is mature and strong enough to deal with hypers, fudders, scammers, dumpers, pumpers etc.

The problem is that it will attract the wrong people if it's not done extremely well. We will have pumps and dumps, maybe the network will grow too fast (in the past, there were a lot of forks, although in the recent months since most people are using 0.4 or 0.5 I wasn't aware of any, but that may change), and we could lose people that are here because they like the technology or the current state of the community. These people wouldn't be attracted at all by "shills" spamming the thread (and the whole forum) with their "buy buy buy" messages.

I know the altcoin circus, I'm here since early 2013 A bad experience I had was the Peercoin "marketing" campaign in late 2013. It attracted a lot of pump and dumpers, and I admit I took the opportunity to sell some Peercoins for a VERY good price (~$10), but the campaign didn't bring forward the coin (technologically-wise) in any way. Peercoin then was forgotten until 2016, when a new dev team began to form from old supporters and new investors, and now they're about to release the first release that is about to change something really substantial - since version 0.3 in 2013! (0.4 and 0.5 were mostly bugfixes and small enhancements)

I have already said that if we reach a milestone - if we have something to tell people - I'm OK with a press release, even if it's a paid one. Another topic I would be OK with would be an article describing Slimcoin's Proof of Burn technology.

Anyway - if someone wants to pay for a press release just to attract "investors" (or pump-and-dumpers) - I cannot hinder him/her and I would also not leave the community because of that. But I would not actively support it.

The project isn't mature enough for this kind of promotion. We should deliver at least web2web to see that we are worth investing in and to show that we are capable team of people - then we can have article. It will show that we are credible and bring more real publicity too with good effect on marketing (not so cheap effect with pumping coin like Bitconnect coin or Bitdeal coin, which are pure s***).

BTW. - if someone want to sell some SLM, I'm open to buy some.

Slightly more reliable, now that I've fixed the error that was preventing blocknotify from successfully updating the RDF graph.

A shell command for returning the timestamp from 24 hours ago:
date --date='-24 hours' +%s
1501286911

A SPARQL query for returning the height of the last block:
PREFIX ccy:
SELECT ?block ?height WHERE { ?block ccy:height ?height } ORDER BY DESC(?height) LIMIT 1

A SPARQL query for returning the height of the last block minted at any given time(stamp), e.g. 24 hours ago:
PREFIX ccy:
SELECT ?height ?dt WHERE {
    ?block ?height .
    ?block ?dt.
  FILTER (?dt < 1501286911)
} ORDER BY DESC(?dt) LIMIT 1

Subtract one height from t'other and you have the number of blocks minted since the given timestamp.

(filter by range: FILTER((?dt < 1501374171) && (?dt > 1498781823)))

I intend to create batch SPARQL queries to instrument the emission rate, tx rate, etc. and cache the results, to feed some more charts in ACME.

Cheers

Graham

Why don't you like it? Let's imagine the most straight and stupid PR campaign ever with tons of money spent on it. If it does the trick and brings publicity wouldn't it bring new talented devs into the project and set the coin price to a new level which also helps a lot because bounties worth way more? What harm could it make? What's downside?

I don't really like this kind of Native Advertising. But if we have reached a milestone (e.g. at the release of the 0.5 stable version, with the OP_RETURN feature and Web2Web working on the main chain), then I would (grudgingly) support it.

I have thought about to start a blog about Slimcoin - maybe on a platform already used by cryptocurrency enthusiasts, like Medium. The articles could then be shared on places like /r/CryptoCurrency. Or on the slimco.in site. The blog could be distributed also in Web2Web form - so we can demonstrate the technology. Other writers would be, obviously, be welcome too.

I say first we develop things we have in plans:
- web2web technology at least and then we can think about article.

What do you think about publishing a press release on Coindesk? It's only $250. And $500 on Cointelegraph. I might probably pay for Coindesk myself in a couple of weeks if Particl goes up. We'd only need a good press release then.

Sometimes when 1 Slim costs $1 it will be remembered as good old times when people mined thousands of dollars worth Slims a day )
We only need marketing team as good as dev team to make it happen. Probably it's time to acquire a new profession.

It seems like Coinmarketcap looks at block explorer on slimcoin.club, doesn't see a number of circulating coins and shows "?". If there was a number, any number, it would show it without checking. And it actually makes sense. CMC doesn't take responsibility for showing right numbers. It only gathers information from coins dev teams which are responsible for correct numbers.

@gjhiggins: I think your stance is reasonable - I am not really a coder, so I can't really evaluate how much complexity would be added by the "totalburntcoins" function - but if there is a working workaround then it's OK for me to postpone that feature. I like the feature, though, and I think it would be good to add it in the future, as these two numbers are two important measures.  Maybe we can add that function when we have a larger development team and more human ressources to control the added complexity.

@dzarmush: The PoW reward today was between 9 and 12 SLM (there are pretty large difficulty swings), that means that if we assume that about half of the blocks are PoW and so a PoW block every 3 minutes, then we have (10,5 * 20 * 24) = 5040 PoW coins mined per day. One must add the PoB coins that are about 1/4 of the blocks (reward = 13 * 10 * 24 = 3120) and the PoS coins but these are not many, maybe 200 or 300 more. So approximately we have 8500-9500 SLM/day mined.

Later I will try if I can do a SPARQL query for the exact number.

How much Slim is being mined a day approximately? I mean total.

So it is time for my 32 cores to make the job a bit more harder

That's what I had concluded to be the only workable approach.

In which case, I'm going to make life considerably easier for myself and everyone else and halt the development work aimed at adding moneysupply and nburnedcoins to the db index because it adds unnecessary complexity to the client and increases the maintenance load  of the codebase.

We already have a solution - the currently unusable-but-functioning importaddress feature addition, implemented in the watch branch with a single commit: https://github.com/slimcoin-project/Slimcoin/commit/a8a9e698a320a04cc5cf0e98ce61bc8e3a87d99d, all neatly packaged for close inspection.

If you recall, I thoughtlessly tested it by importing the first address to hand, the burn address and the client went into paroxysms of fevered CPU activity, trying to calculate a stake for the 5000-plus tx history. Setting reserveblance should cure that issue and a small HTML/JSON wrapper that publishes  getinfo on demand is what we're interested in because it will contain i) an accurate and direct report of the moneysupply and ii) an accurate and direct report of the total number of coins sent to the (unspendable) burn address.

The problem is reduced to that of maintaining a specifically-compiled Slimcoin node and a small wrapper. In the interim, I'll reconfigure the two Slimcoin empty-walleted clients that ACME interrogates (mainnet and testnet, both clients configured to use BerkeleyDB 4.8 to allow usable datadir snapshots) to be watch-address clients tracking the mainnet burn address and the testnet burn addresses respectively. This will allow nburnedcoins to be reported directly using the battle-tested client code instead of a report based on querying a less-than-reliable, over-complex SPARQL/RDF setup.

Using the above strategy (compiling a client for the feature.watch branch), I will create a community resource devops solution that is as trivially deployable as I can manage * and I'll fund an initial instance for 12 months, that should see us through the next stage.

Comments, observations, suggestions, welcome.

Cheers

Graham

* https://groupon.github.io/ansible-silo/ <- docker-specific but that's okay

Woow. The hashrate and diff is really high now...
Who set up botnet ? Because I can't believe 10x hash rate of just 1-2 weeks ago.

The problem is that I'm almost sure that services like Coinmarketcap do not run their own altcoin clients (they would have to run about 1000 clients) and so they rely on a single point of failure anyway. If the "total burnt coins" function is included into the code it would be ideal, so I fully support your approach. But anyway we would have to wait until a block explorer exposes the number "to the public" until CMC can use it, but even then the "single point of failure" problem would persist. For example, if ACME goes into "production", in theory the instance that was communicated to Coinmarketcap could be manipulated.

So the single point of failure problem in my opinion should be solved by redundancy, more than one source should be provided to them. This can already be done: My idea, if I continue with the "scraping" approach, is to provide the easily-readable source (my web service), the "source of the source" (bchain.info) and an alternative source (slimcoin.club) they always can check, and to publish the script at Github or a similar repository (I wrote a Python prototype with less than 50 lines of code).

That would be the "short term solution", and later, when ACME is finished and open sourced, then I think it should be hosted by more members of the community, so we have redundancy and a better service. I'm interested to run it if the VPS that runs my Slimcoin client supports it.