Transcluded from its own thread: I've had a number of people approach me about their coins getting attacked by having the blockchain replaced with a longer chain, the longer chain released by the attacker is without certain transactions. The coin may be attacked but the target is normally an exchange, coins are sent to the exchange, sold for Bitcoin and then withdrawn, at that points the longer chain is released, the coins disappear from the exchange and the attacker gets their coins back. Small coins with low hash power are easy targets for attackers. This has caused a few coin pairs to be frozen and people to be in a panic. PoW coins are the typical target for this type of attack, PoS coins are harder to target due to PoS block generation but not impossible if PoS generation is still very low. There have been many proposals for solutions to protect coins from a blockchain replacement attacks but for small coins the one solution that works and is available now is to use live checkpointing. Checkpoints are defined in Bitcoin source code by defining a block hash and height, clients will only connect to a chain that has the corresponding blocks, it is to make sure that clients connect to the correct main chain. Altcoins inherit this checkpoint system. Realtime checkpointing was devised by SunnyKing developer of PeerCoin to protect the chain before PoS was sufficient. It protects the history of the chain by use of a node that will broadcast checkpoints at a certain height set in the conf file. If your coin is being attacked, your coin pair is locked on the exchange and you face potential delisting you may want to consider implementing realtime checkpointing. For reference there is a commit for checkpointing below (Deepcoin linked below was commissioned and not a project that I ran personally), instructions on how to use it is in the checkpointsync.cpp file. If you decide to use this system add a Peercoin copyright notice on the About dialog and COPYING file. https://github.com/Deepcoinbiz/Deepcoin/commit/43413fac89da1db064668e7e4dd5bd6c6036dfb4I've recently disabled this code in Slimcoin because as implemented, it relies upon a centralised solution. If this code were re-enabled in Slimcoin, it would result in someone potentially having exclusive control over both the centralised checkpointing node and the centralised checkpointing privkey and, by extension, the network. I consider this to be a more potent and serious existential threat to the network than that posed by a naturally-occurring condition which might conceivably be addressed without compromising the basic principles of operation. Peter acknowledges other solutions but the problem is rooted in a systemic weakness inherited from Bitcoin - the very notion of checkpoints is a feature of an improperly decentralised network. Here's a thought experiment for you: Slimcoin already has checkpoints, they're added by hand to the source file src/checkpoints.cpp: current “slimcoin” v0.4: https://github.com/slimcoin-project/Slimcoin/blob/slimcoin/src/checkpoints.cpp#L27in-test “master” v0.5 https://github.com/slimcoin-project/Slimcoin/blob/master/src/checkpoints.cpp#L27// What makes a good checkpoint block?
// + Is surrounded by blocks with reasonable timestamps
// (no blocks before with a timestamp after, none after with
// timestamp before)
// + Contains no strange transactions
Which invites the question: “So, in a peer-to-peer networked cryptocurrency exactly whose responsibility is it to: calculate fresh checkpoints, edit the code, ensure the change is propagated to all copies of the source, compile a new release, make platform-specific binaries available as a boon to those incapable of generating the binaries themselves and ensure that notification of the updated list of checkpoints is published in all the proper channels?” And is that to be monthly, bi-monthly or quarterly? And a supplementary question: “Who do you think is doing that right now?” Leading to the penultimate: “And just how long do you think that will last?” And ultimately: “orly?” (Answers to the not-entirely-tangential question “What defines a ‘strange’ transaction?” on a postcard, please.)Or, we can simply thrash out the absolute minimum that needs to be done and establish a human-based solution that shares out the work/reward on an equitable basis. No prizes for guessing which direction I consider to be of greater long-term benefit to the network. Sub-topic IVa: Who's doing outreach for Slimcoin? Who considers it their responsibility to contact the exchanges currently hosting Slimcoin nodes, to gain their input and to present it for community information/consideration? Cheers Graham |
|
|
|
I believe we should begin making the necessary steps to gain $SLM listing on Cryptopia.
They've recently delisted Sprouts, complaining that the wallet kept crashing for them. They would likely have an identical experience with the Slimcoin wallet. Cheers Graham |
|
|
|
Today there are over 750 cryptocoins in existence.
750 4000Yep, ticks all the boxes to be an economist: no idea of the actual state of play, no insights to bring but nevertheless unable to resist pointlessly churning out patronising kneejerk ideology. 100% economist and troll of the year, yes indeed. +10. Cheers Graham |
|
|
|
Can the key generator be safely used via standard HTTP?
No need ... https://iancoleman.github.io/bip39/Offline Usage You can use this tool without having to be online. In your browser, select file save-as, and save this page as a file. Double-click that file to open it in a browser on any offline computer. Alternatively, download the file from the repository - https://github.com/iancoleman/bip39Cheers Graham |
|
|
|
Do you think they can implement in wallet burning coins function?
I'm not familar with the implementation but my educated guess is that they'd have to work explicitly to stop it. The term “burning” is, in essence, a UI confection to help users establish a mental model of an abstract domain which can neither be directly inspected nor directly manipulated - the software acts a mediator in both cases, interpreting the domain to the user via analogies in order to avoid forcing the user to work with the underlying cryptography functions. The analogy uses a model of addresses, accounts and transactions to represent the operation of cryptography functions and the resulting state changes. The analogy (or more properly in this case, metaphor) is a weak model and the originators failed to understand the full impact on the user of presenting such a weak model. Simply sending coins to the burn address === “burning the coins”. This can be done in any Slimcoin client that conforms to the comms protocols - be it by clicking a button on a GUI or submitting a JSON-RPC sendto request to a headless daemon's API, irrespective of whether the client is implemented in C++, Java, Javascript or LISP. As Slimcoin users, we are observing a convention (and make no bones about it, it is just a convention) that the coins are then unrecoverable and can be subtracted from the total number of coins in circulation. The software in the reference clients (those actually laying down blocks) treats such transactions as special and instead of calculating a PoS, it calculates a low diff PoW hash which is coded to have an increased probability of winning the block. The address which is listed in the burn tx's txin (i.e the address which funded the burn tx) is credited with the reward if the PoB guess actually wins. The PoB factor for that tx is decremented with each try (win or lose) and so the burned coins are described as subject to “decay” (another metaphor of questionable merit). Cheers Graham |
|
|
|
Why i cant see on the slimcoind-qt the minning button or Graphics about the difficulty ,either a counter of Slimcoin that I all ready mine.
If you can post a screenshot and provide some information about your setup, that would give group members at least a chance of making helpful suggestions. Cheers Graham |
|
|
|
told you so Dept: With reference to posts passim, I find I share much of author Jamie Bartlett's take on things which he articulates in an article in the Guardian titled Forget far-right populism – crypto-anarchists are the new masters. And yes, he does mean us. Cheers Graham Edit: tangentially but not unrelatedly, the Office of National Statistics asserts that there are currently just short of 32 million jobholders in the UK, suggesting that the future promises to be quite different. |
|
|
|
Windows
Version? (nearly there) nm Old Windows: ${HOME}\Application Data\SLIMCoin\debug.log New Windows: ${HOME}\Application Data\Roaming\SLIMCoin\debug.log Cheers Graham |
|
|
|
Where is located that log file?
What operating system? |
|
|
|
fwiw dept: I've pointed my home-grown “ACME” block explorer at my datacoin node and it's returning basic block and tx info. Addresses remain problematic and I've yet to add the data explorer. https://minkiz.co/acmeCheers Graham |
|
|
|
But, where i can see the activity of the program when is minning?
in the log file Cheers Graham |
|
|
|
How i can start minning using slimcoind-qt ? , because i dont see the minning button.
Open the debug window / rpc console and enter: help setgeneratesetgenerate <generate> [genproclimit]
<generate> is true or false to turn generation on or off.
Generation is limited to [genproclimit] processors, -1 is unlimited.
and help getgenerategetgenerate
Returns true or false.
The built-in miner is known to be slow in comparison to the optimized companion CPU/GPU miner implementations (see posts upthread and the previous thread for details). Cheers Graham |
|
|
|
Do you how big is the PoS block reward?
Thank you! Then there's the stuff in main.h https://github.com/slimcoin-project/Slimcoin/blob/slimcoin/src/main.h#L108 (up from there as well as down) which defines the variables for reference in main.cpp: //Adjusts PoB and PoS targets
extern const uint64 POB_POS_TARGET_SWITCH_TIME;
But then you have to grep -rn POB_POS_TARGET_SWITCH_TIME src/* to find out where it's bound, consulted, sent to /dev/null, etc. Cheers Graham |
|
|
|
(*) or whatever value is viewed by the cognoscenti to be appropriate for a “starter kit” approach.
10 coins is not enough for a regular PoB income. You will probably find some blocks, but don't expect this to occur very fast (in some months, perhaps). The rate of "findings" is random, so it can be today, or in one year.
100 or even better 200 SLM coins, for now, are costing only 10-20 USD cents and you have a real chance to find blocks regularly if you burn them (one in about 1-2 weeks).
Cheers Graham |
|
|
|
Draggin' this over from the old thread ... I am mostly a Peercoiner but Slimcoin has gotten my attention because of it being the first proof of burn currency, at first that was a slight curiosity but after trying it out I noticed one thing. Slimcoin has a much better incentive to keep a node online all the time than Peercoin, in fact since I burned some coins my node has pretty much stayed up constantly. I don't want to turn it off because I would miss out on collecting (these admittedly almost worthless) tokens.
...
Anyway, I was thinking of ways to increase adoption of Slimcoin, not just to have people buying a few as a speculation but to actually have them burn some and become part of the network. My idea is this: change the protocol so that when you burn coins you can specify the burned coins to be associated with a different address instead of the one you burned from. This would allow me to send someone burned coins but it would not allow for the trading of burned coins. A faucet and reddit tip bot could be setup for people who would like to try minting with Slimcoin and you could actually give people a decent amount without worrying that they would immediately sell for their favorite currency.
Perhaps create a BIP38 “2FA” paperwallet “Gift Token” of 100 SLM (*) with 90 already burned, leaving 10 SLM to allow plenty of opportunity to play with the inscription feature. The client generates the paperwallet address (read: the ECC priv/pub keypair) on behalf of the person operating the client so the privkey can be used (forcibly, on behalf of the recipient) to burn 90 SLM before the paperwallet is even printed with the address (WIF-formatted pubkey) and the encrypted privkey (the password to which is the 2nd “F” in “2FA” and must be communicated via a separate channel). Or have I missed some showstopper that is obvious to everyone except me? (*) or whatever value is viewed by the cognoscenti to be appropriate for a “starter kit” approach. Cheers Graham |
|
|
|
|
Show Posts
