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

Hello all,

Is anyone interested in a new ARM binary? If so, do people think that the latest version is stable enough to use for it?

Regards

Works well. Restart wallet and it will show up. That was the case with all version

Dunno, it beats me, something to do with more recent versions of Qt maybe? I've found it corrects itself on restarting the client, at least on Linux Mint/Ubuntu 18.

Cheers

Graham

nevermind for POW
why 0.6.0 wallet don't see my NET BURNT COINS against of 0.5.0 ?

Changes to release candidate

I've made a couple of adjustments to the release candidate

1. I removed the inscription listing because atm it's more trouble than its worth in terms of causing refresh updates on receipt of "newly-minted" blocks whilst syncing.

2. I re-enabled UPNP - which had been inadvertently pernanently disabled some time ago:

https://github.com/kryptoslab/slimcoin/commit/0119fd0b8802d57e8c7421590f44cef9644a8d74#diff-9a82240fe7dfe86564178691cc57f2f1

The culprit is the new line #20 of net.cpp ... #undef USE_UPNP. I dunno who added it but I'll bet that they didn't mean to let it sit there permanently. Anyway, I nuked it and Slimcoin now successfully negotiates UPNP - so with any luck we'll see more than 4 - 5 nodes configured with listen=1.

If I were to be brutal and describe the situation In torrrent terms, listen=1 is seeding and listen=0 is leeching. When the chainz explorer see 25/30 nodes, only half a dozen are actually fully supporting the network by broadcasting txs, the rest just aren't listening. In the words of Don McLean [1] ... "Perhaps they'll listen now."

Cheers

Graham

[1] https://www.youtube.com/watch?v=oxHnRfhDmrk ("Vincent", aka "Starry, starry night.").

Looks like the majority of recent blocks (around your time of posting or around block 1736975, respectively) was extracted by PoS while a majority of the PoW blocks was mined by SViDg1EJaW71r5FENejW8522WpEXvRPcDs.
A big PoW miner and coins not staking for some time going online taking the lion's share.
Business as usual.

Slack is gone, I don't even know what is going on there - my account has "disappeared".

Discord and telegram, on telegram there are more people, because ... it wasn't deleted.

I'll try to set up Discord-Telegram cross-bridge.

Website will have to be updated also - especially regarding new wallet version to download.

Done. Thanks to everyone, especially Graham for the new version! I'm currently very busy and thus I'm also delayed with my "Slimweb node" plans, that have been moved to Q3 2019 in the "roadmap" of the OP. That doesn't mean that it will be "Duke Nukem Forever": The nodes are already online, only the Fuseki and Torrent software still have to be configured and installed.

Question: The Slack link is not working, can it be deleted? I think chat has moved to Discord completely, or not?

https://discord.gg/ffeDjmV - new server with link that will never expiry.
@d5000 - please update it.

News from Novaexchanges.

Got the same problem.

https://novaexchange.com/market/BTC_SLM – page not found. And withdrawal is still disabled. Emailed their support, waiting for the answer.

Upd: They've just posted an announcement: "SLM - SlimCoin markets have been paused for a while. We are fixing some issues with the wallet, and we will soon open the BTC markets again. Apologies for the inconvenience!".

why my HR is about 2.5 kHs, network HR about 70-80 (!) H/s and still no blocks in a day ?

Graham,

Whoa! Awesome work, thank you for all your efforts, time and work!
Even compiles on Wheezy again, so I could finally update my node.
Performance and resource usage greatly improved too.

Still resynching, but totally excited from the progress in Slimcoin.

Cheers - psycodad

That would be useful. IME, an altcoin's DIscord server is now the first port of call for exchange devs seeking support.

Cheers

Graham

I think owner have deleted it, as I wasn't the owner of the server, just one guy that have created it earlier. Because of that I didn't also have full admin privileges.
If it was him, that was quite a move...
It seems that it's gone.

Edit: yes, owner has deleted...

I will create one in, and hook up telegram bridge.

What happened to the Discord server?

Cheers

Graham

Happy 5th anniversary!

Nicely done Graham. I don't know, when you were working on this, but it was a quiet work, I just saw your commits to github repo, and a few hours later release.

Will try to sync now.

Syncing looks quite fast, big improvement vs. 0.5.x

SLIMCoin 5th anniversary

Slimcoin's 5th anniversary is imminent, according to the genesis block: main.cpp:

The timestamp 1399578460 decodes to “Thu  8 May 20:47:40 BST 2014”.

Happy 5th Birthday Slimcoin
I thought a couple of birthday presents were in order. Firstly, the chainz block explorer is now funded for the next 6 months and secondly ...

SLIMCoin v0.6 pre-release
I have integrated the completed development work into the master branch and have changed the Slimcoin-project default branch from slimcoin to master. I'm calling the result SLIMCoin v0.6 (not that I can persuade the client to advertise itself as such, ho hum) and have cut a pre-release, now available from Github: https://github.com/slimcoin-project/Slimcoin/releases/tag/SLMv0.6.0.

Upgrading to V0.6 necessitates a resync
When I came to look more closely at why the burnt coins total wasn't working properly, I discovered that I'd apparently omitted a key piece of code, the one that makes the difference because the change causes the client to reject the block index because until the block index is rebuilt, it doesn't contain the expected slot for totalburned. Rebuilding the block index isn't difficult, just delete the index file (blkindex.dat) and the log file(s) in database and restart the client with the -loadblock option set to the location of blk0001.dat (I rename it to blockchain.dat, just for clarity.)

An alternative approach would be to nuke blkindex.dat and the contents of database, rename blk0001.dat to bootstrap.dat and then start the client as normal, the v0.6 client will detect the bootstrap file and will load from it, building the index as it goes. Our rented i5 Hetzner box took around two and a half days to complete the exercise.

Or you could junk everything other than the wallet and sync from 0. That'd work too. Or you can use the one I built on the server and made available as datadir.zip, it contains

What's in the v0.6 box

Additions

• Load from bootstrap.dat if present
• `addnode (onetry)` RPC command
• Encrypt/Decrypt message facility
• Mining tab
• Wallet/tx fix/zap facility
• ClearOphans option for Transaction View
• Coin control
• CHECKLOCKTIMEVERIFY
• "totalburnt" in getinfo results
• `dumpbootstrap` RPC command
• Account Report tab
• Sign/Verify message dialog
• Reservebalance spinbox
• Multi-sig create/spend dialog
• torrenthash publishing / inscriptions via OP_RETURN
• walletnotify

Housekeeping

• Add support for miniupnpc api versions 14, 16 and now 21
• Add Python-implemented Slimcoin blockchain reader
• Repair indexing of accumulating total burned coins
• Relay OP_RETURN TxOut as standard transaction type
• Extend MAX_OP_RETURN_RELAY 80 -> 100
• Disable unused centralised sync-checkpoint facility.

Improvements to automated testing

• Enable Travis CI continuous integration
• Update and expand tests

Contributions

• Integrate barrystyle's batch RPC PR
• Added compile documentation for Arch linux via PR from eddycurrently/doc_updates
• Implement Johnny Latte's SHA256 speed-up.

Garnered from abroad

• Fix OpenSSL v1.1 compatibility - Cherry-picked from Peercoin 0.6 rc1
• Merge remote-tracking branch 'ppcoin/master' into refactor.ppcoin
• Backport bitcoin commits (various)

Cheers

Graham