Slimcoin | First Proof of Burn currency | Decentralized Web

[gjhiggins]

In case it's of interest to anyone ...

It transpires that the adapted Spreadcoin customised address generator produces uncompressed keys - this explains why the customisation is lost on importing the (uncompressed) privkey.

As evidenced by the addresses shown in the wallet, Slimcoin takes a compressed-key-by-default approach, inherited from PPCoin.

This was the original output from makekeypair before I adjusted it (prematurely, it would seem) to remove the uncompressed part:

  * secret (hex): f092e90100000000c693e90100000000c693e901000000000000000000000000
  * : uncompressed
    * secret (base58): 7S78qD9aBwpiCNCZsx9BmMKtsLY58p2zWKftnSPJkyV1SQULjGz
    * pubkey (hex): 0480d647bf15e05abcad608725c56fd7722a76335ad248fcf4032f7ae7d3ae09be4b13b00a4853b bf4cd00a1b1812cd401da8386405613a4927110e1db4cf21f19
    * address (base58): SkM4auwYLe4R59zkXFnVJ3tCzCkZGms9cu
  * : compressed
    * secret (base58): VPp5ZncqVJyaqAa47tP8WkiPwBE9FUbnpRQfZZ3TP6Jcvtmy6WWR
    * pubkey (hex): 0380d647bf15e05abcad608725c56fd7722a76335ad248fcf4032f7ae7d3ae09be
    * address (base58): Siy45aBFsMzqtDEik4taLgDucHm5Tf1BdR


The difference between compressed and uncompressed being:

Code:

def test_get_uncompressed_pubkey_from_compressed_pubkey():
    """
    Uncompressed pubkey from compressed pubkey
    """
    def pow_mod(x, y, z):
        "Calculate (x ** y) % z efficiently."
        number = 1
        while y:
            if y & 1:
                number = number * x % z
            y >>= 1
            x = x * x % z
        return number
    compressed_key = "0380d647bf15e05abcad608725c56fd7722a76335ad248fcf4032f7ae7d3ae09be"
    p = 0xfffffffffffffffffffffffffffffffffffffffffffffffffffffffefffffc2f
    y_parity = int(compressed_key[:2]) - 2
    x = int(compressed_key[2:], 16)
    a = (pow_mod(x, 3, p) + 7) % p
    y = pow_mod(a, (p + 1) // 4, p)
    if y % 2 != y_parity:
        y = -y % p
    uncompressed_key = '04{:x}{:x}'.format(x, y)
    print(uncompressed_key)
    # 0480d647bf15e05abcad608725c56fd7722a76335ad248fcf4032f7ae7d3ae09be4b13b00a4853bbf4cd00a1b1812cd401da8386405613a4927110e1db4cf21f19

Anyway, in the course of getting to the nitty-gritty of the compressed/uncompressed issue, I forked bip32.org’s javascript-hosted Hierarchical Deterministic Key Generator, configured it to use an extended public/private keypair of my own invention that I considered appropriate for Slimcoin  - spub (0xef6adf10) and sprv (0xef69ea80), committed the changes and configured the github pages rendering.

It's a standalone web page which can be hosted locally, disconnected from the net, for extra peace of mind.

Cheers

Graham

[1713960970]

1713960970

[1713960970]

1713960970

[1713960970]

1713960970

[PeterTheGrape]

I'm understanding that is a paper wallet generator, and possibly can be used to create keys from a phrase as well, https://en.bitcoin.it/wiki/Deterministic_wallet but not sure beyond that,

I went to https://github.com/slimcoin-project/slmbip32.github.io and pasted the html text onto a txt document and changed it to html. It came up with a "BIP32 Deterministic Key Generator" I entered a password and that's as far as I got.

Like most people I'll wait for the one click version. 

[gjhiggins]

I'm understanding that is a paper wallet generator, and possibly can be used to create keys from a phrase as well

It's not a paper wallet generator, despite the appearance of a QR code graphic ...

A deterministic wallet is a system of deriving keys from a single starting point known as a seed. The seed allows a user to easily back up and restore a wallet without needing any other information and can in some cases allow the creation of public addresses without the knowledge of the private key. - https://en.bitcoin.it/wiki/Deterministic_Wallet

The first feature is your “one ring to bind them all” deal. The magic (seed) phrase “collect house buttery stable” will enable me to recover all of the privkeys generated from this seed (the parent private key or “privkey”) and thereby enable to me to take control of any and all UTXOs associated with those privkeys (which, AIUI, are actually an encoding of the parameters for the selected ECC scheme).

The second feature is important for online sales, allowing a merchant such as myself (they are really cool digital prints) to enable my remote server to create receiving addresses for incoming payments without needing the privkey (which otherwise would be exposed to attack on the server).

Like most people I'll wait for the one click version.  

Unfortunately (1), that is the one-click solution.

Unfortunately (2), to be effective, one-click solutions require that users already have a reliable mental model that is sufficiently accurate and detailed to adequately inform the choice that they are faced with. Few people would be comfortable with a one-click solution for submitting tax returns that basically translated to: “Here's all my money, take whatever you want”.

Users aren't always in the best position to articulate their interface requirements because they typically don't have access to domain fundamentals such as ...

The levels-of-processing effect, identified by Fergus I. M. Craik and Robert S. Lockhart in 1972, describes memory recall of stimuli as a function of the depth of mental processing. Deeper levels of analysis produce more elaborate, longer-lasting, and stronger memory traces than shallow levels of analysis. Depth of processing falls on a shallow to deep continuum. Shallow processing (e.g., processing based on phonemic and orthographic components) leads to a fragile memory trace that is susceptible to rapid decay. Conversely, deep processing (e.g., semantic processing) results in a more durable memory trace.
- https://en.wikipedia.org/wiki/Levels-of-processing_effect

The above is broadly describable as falling under the remit of “user task analysis” and “user information requirements analysis”- what the task is in terms of cognitive processes and their functioning, what information is known to be required to inform those cognitive process, how that information is best presented to integrate effectively with the cognitive processes, how to account for known effects of perceptual distortions, characteristics and limitations of short-/long-term memory performance and ditto for the limits of attentional performance.

The ability to selectively process information (attention) and to retain information in
an accessible state (working memory) are critical aspects of our cognitive capacities.
While there has been much work devoted to understanding attention and working
memory, the nature of the relationship between these constructs is not well understood.
Indeed, while neither attention nor working memory represent a uniform set of processes,
theories of their relationship tend to focus on only some aspects. This review of the
literature examines the role of perceptual and central attention in the encoding,
maintenance, and manipulation of information in working memory. While attention and
working memory were found to interact closely during encoding and manipulation, the
evidence suggests a limited role of attention in the maintenance of information.
Additionally, only central attention was found to be necessary for manipulating
information in working memory. This suggests that theories should consider the
multifaceted nature of attention and working memory. The review concludes with a
model describing how attention and working memory interact.

- http://visionlab.harvard.edu/Members/darylfougnie/Daryl_Fougnie_%28Academic%29/Home_files/Fougnie-in%20press-chap%201.pdf

As a cognitive psychologist by discipline, to me this stuff is just basic characteristics of the standard i/o routines known to be reliably present in the typical installation of the “HomSap v1.0” wetware OS and it's just an irrational aberrance of modern life that people are, by and large, comfortably oblivious to the (entirely predictable) limitations of their own particular installation of HomSap 1.0.

Cheers

Graham

The UI for addresses is pretty naff

Q.E.D.

[gjhiggins]

I went to https://github.com/slimcoin-project/slmbip32.github.io and pasted the html text onto a txt document and changed it to html. It came up with a "BIP32 Deterministic Key Generator" I entered a password and that's as far as I got.

I've found that contemporary browsers will no longer execute JS in opened files of HTML (check the JS console in the browser or the browser log for messages to this effect). In order to function, the page needs to be hosted by an HTTP server locally (or, at least for Chromium, a command-line option must explicitly be provided).

The GH page version will work just fine as an app and is as private as any github HTTPS connection (so, vulnerable to MITM conducted by your local sovereign state TLA actor).

Nevertheless, perhaps stealingadapting Ian Coleman’s BIP39 JS solution would be preferable.

Cheers

Graham

[gjhiggins]

Nevertheless, perhaps stealingadapting Ian Coleman’s BIP39 JS solution would be preferable.

Done.

Added https://github.com/slimcoin-project/bip39, the instructions seem reasonably clear.

I don't know the 8th-level mage's spell of get-gh-to-use-a-nonstandard-index that Ian incanted in order to get the app to run under GH pages but I shall ask.

This one should download, open and run in the browser as a standalone HTML+JS app.

Cheers

Graham

[aIA]

Added https://github.com/slimcoin-project/bip39, the instructions seem reasonably clear.

Thank you for all you hard work Graham!!!

I think it would be a nice feature that any user can create offline address with their mnemonic passphrase (as paper wallet style) and add in the client as "only read" (like omniwallet) in order to control their funds and if later they need move their coin could add the passphrase in order to get private key for signing tx.


What do you think about?

Greetings.

[PeterTheGrape]

... The magic (seed) phrase “collect house buttery stable” will enable me to recover all of the privkeys generated from this seed (the parent private key or “privkey”) and thereby enable to me to ...

...

As a cognitive psychologist by discipline, to me this stuff is just basic characteristics of the standard i/o routines known to be reliably present in the typical installation of the “HomSap v1.0” wetware OS and it's just an irrational aberrance of modern life that people are, by and large, comfortably oblivious to the (entirely predictable) limitations of their own particular installation of HomSap 1.0.

...

Just out of curiousity, is this how it works?

1) The wallet can generate a huge number of private keys, too many to access obviously.

2) A seed phrase reduces the number of possibilities from "an extreme number" to a certain range like a thousand or a million keys.

I noticed in one wallet, I think electrum or multibit, there is a file called 'dictionary' that has a list of a few hundred or so words that can be used to generate a key. It occured to me then that this was wide open to problems, since people would try to selectively used certain combinations of words as their 'secret seed phrase'.

As for cognitive psychology, I know it is all the rage now, and of course it will appear 'successful' in a society that is based on a cognitive approach to everything.

But it always disappoints me to see people who have an interest in psychology, the working of the mind, then regress to a cognitive approach. In my opinion analytical psychology, Jung et al, is a psychology. It studies the mind in the context of its environment, history and so on. Other approaches, like cognitive psychology, are more autopsy based.

[gjhiggins]

Just out of curiousity, is this how it works?

More like this:



(Transcluded from the Bitcoin wiki entry for BIP 32)

The seed is 32 bits of output from any acceptable source of entropic bits (YMMV). Using dictionaries of words is just one approach.

Cheers

Graham

[muf18]

Hello dev @gjhiggins. Can you reply to my PM ? Sorry for poking you here, but maybe you didn't see it.
My second question - what makes dcrypt that it's ASIC proof ? It doesn't use so many memory, and so scrypt was eventually made asic, so I don't how this ASIC-proof?

[d5000]

My second question - what makes dcrypt that it's ASIC proof ? It doesn't use so many memory, and so scrypt was eventually made asic, so I don't how this ASIC-proof?

Look at the whitepaper:

The Dcrypt algorithm is a “front-end” to the SHA256 hashing algorithm. Its main purpose is to prevent an ASIC dominated
proof-of-work mining scheme from occurring in Slimcoin. Allowing Slimcoin to become ASIC minable will overshadow
the proof-of-burn and proof-of-stake aspects of the coin. Dcrypt is made to be difficult to parallelize, require significant
amounts of memory, require significant amounts of reading/writing to/from memory. Also, the amount of memory required
is not a predetermined size. The hashing algorithm loops until a specific condition is met and for each loop, the size
increases.

Slimcoin Whitepaper

[muf18]

Ok, I didn't see whitepaper.
But still it doesn't use whole lot of mem, so I don't if it so 'proof'. Parallelize yeah, but still not for now, because this has one attention, but in the future it can be achievable.
Also interesting would be too see if slimcoin, could be upgraded to segwit or introduce zerocoin protocol.

[PeterTheGrape]

...
Also interesting would be too see if slimcoin, could be upgraded to segwit or introduce zerocoin protocol.

Because distribution is so flat, over such a long period of time, almost any feature from any other coin would be worth more cloned into slim than on the original coin.    eventually at least For now the premined and ico coins seem to be winning

[d5000]

@gjhiggins: Thank you again for excellent work and explanation!

I hopefully will find some time to work on the github.io website this weekend, so I will try to integrate/link the key generator into it. Is there a problem if I rename the repo to, let's say "keygenerator", so the URL is prettier?

Also interesting would be too see if slimcoin, could be upgraded to segwit or introduce zerocoin protocol.

Slimcoin is based on the Peercoin codebase (with the Proof of Burn addition and some other minor additions), so the easiest way to go for Segwit and other modern features would to port these features when Peercoin introduces them. I've asked the Peercoin devs some days ago and they plan to base version 0.7 (0.6 is the actual development version, 0.5 the stable verson) on a recent Bitcoin version with Segwit.

In the case they don't implement it in the coming years, an alternative Peercoin-based coin with a very recent codebase is NAVCoin.

It's not a short-term goal though. From my point of view first a generous time should be used to test the current 0.5 client and its new features.

[Sorai]

I tried installing the OS wallet and I got 1 connection to the network for a while, but then it stopped connecting to the network.  Has anyone had success with the OS wallet? 

[gjhiggins]

I think it would be a nice feature that any user can create offline address with their mnemonic passphrase (as paper wallet style) and add in the client as "only read" (like omniwallet) in order to control their funds and if later they need move their coin could add the passphrase in order to get private key for signing tx.

It's funny you should mention that. I found this gist lurking on github:

https://gist.github.com/WyseNynja/8120948

It's a distillation of laanwj's bitcoin commit that implements just such a beast and at first glance, it does seem logical to embrace that power-up for wallet users. Unfortunately, the transactions associated with watch-only addresses would need to be explicitly prevented from being considered in stake calculations - which is a whole other ball game.

Cheers

Graham

[gjhiggins]

I think it would be a nice feature that any user can create offline address with their mnemonic passphrase (as paper wallet style) and add in the client as "only read" (like omniwallet) in order to control their funds and if later they need move their coin could add the passphrase in order to get private key for signing tx.

It's funny you should mention that. I found this gist lurking on github:

Here it is in action - I took a fresh wallet and imported both the general and bounty donation addresses as part of an exercise prompted by remembering to demonstrate that the original QRCode image generation facility still works as expected with watch-only addresses:



and I can take the opportunity to expose the ugly reality of the UI presentation:



And when the watch-only txs are admixed with the ordinary-but-indistinguishable tx associated with one's own addresses, it becomes a right dog's breakfast. Aaaand the tx date is incorrectly shown in the listing - which is why a separate listing will be required for txs associated with watch-only addresses

If I can find a single point in the stake-calculating code which can be used to filter out watch-only addresses from the rest (any address without a privkey is a watch-only address) and I can persuade the wallet to filter out the watch-only txs from the overview and I can create a duplicate of the tx listing that is specialised to watch-only addresses then we could be in business.

Cheers

Graham

[Sorai]

Looks like I got 4 connections this time around, so my Mac wallet may be functioning properly now.   

I recall reading back on this thread somewhere someone commenting that Slimcoin minting can be CPU intensive.  Is it OK to run Slimcoin wallet on a computer that has other wallets running, or will it hog too much of the processing power? In other words, do I need to dedicate a computer to a Slimcoin wallet open for staking/burning?

[gavrilo77]

Looks like I got 4 connections this time around, so my Mac wallet may be functioning properly now.   

I recall reading back on this thread somewhere someone commenting that Slimcoin minting can be CPU intensive.  Is it OK to run Slimcoin wallet on a computer that has other wallets running, or will it hog too much of the processing power? In other words, do I need to dedicate a computer to a Slimcoin wallet open for staking/burning?

Minting by CPU is intensive like the other CPU coins, depend how many cores you will dedicate for mining. Staking is CPU intensive, but you dont need to stake 24/7. I allow staking every few months for one day. All staked coins coming. Burning is not CPU intensive.

[Sorai]

Looks like I got 4 connections this time around, so my Mac wallet may be functioning properly now.   

I recall reading back on this thread somewhere someone commenting that Slimcoin minting can be CPU intensive.  Is it OK to run Slimcoin wallet on a computer that has other wallets running, or will it hog too much of the processing power? In other words, do I need to dedicate a computer to a Slimcoin wallet open for staking/burning?

Minting by CPU is intensive like the other CPU coins, depend how many cores you will dedicate for mining. Staking is CPU intensive, but you dont need to stake 24/7. I allow staking every few months for one day. All staked coins coming. Burning is not CPU intensive.

I wasn't planning on mining, only staking. (Since I don't know how to mine).   

My other POS coins seem to require 24/7 staking.  I assumed all coins had to be staked 24/7 to earn anywhere near your maximum eligible staking rewards.  Is there something special about Slimcoin that lets you get away with doing it every few months for a day?  When you say "all staked coins coming" do you mean you're not missing out on any rewards by not staking continually?   
 

[gavrilo77]

Looks like I got 4 connections this time around, so my Mac wallet may be functioning properly now.  

I recall reading back on this thread somewhere someone commenting that Slimcoin minting can be CPU intensive.  Is it OK to run Slimcoin wallet on a computer that has other wallets running, or will it hog too much of the processing power? In other words, do I need to dedicate a computer to a Slimcoin wallet open for staking/burning?

Minting by CPU is intensive like the other CPU coins, depend how many cores you will dedicate for mining. Staking is CPU intensive, but you dont need to stake 24/7. I allow staking every few months for one day. All staked coins coming. Burning is not CPU intensive.

I wasn't planning on mining, only staking. (Since I don't know how to mine).  

My other POS coins seem to require 24/7 staking.  I assumed all coins had to be staked 24/7 to earn anywhere near your maximum eligible staking rewards.  Is there something special about Slimcoin that lets you get away with doing it every few months for a day?  When you say "all staked coins coming" do you mean you're not missing out on any rewards by not staking continually?  
 

Use this link for CPU miner. Just change your user and pass in .bat file inside and the number of cores.

https://mega.nz/#!ewEl0RiJ!v7NgPRz3pVhUMN3vkB9eZnTEma774kdujfgk2qLGMdE

Another link

https://mega.nz/#!KttQjaRK!RCO2NeGe8U5fIgdm0i3Lp6I-FVYjSmqPXDntgI7z1yM (it is stable with hashtable 4, dont go 5)


As per my experience, i did not stake for more than a two years (i did not know how ), once i allow staking a thousands of SLM came to my wallet. Since that time i am doing it every few months.

To get SLM from burnt coins you must have open wallet 24/7