Author

Topic: [ANN] SpreadCoin | Decentralize Everything (decentralized blockexplorer coming) - page 289. (Read 790393 times)

legendary
Activity: 1484
Merit: 1007
spreadcoin.info
Building decentralized web on nodes - interesting

https://youtu.be/999q3_htKPU?t=8m58s

edit

https://github.com/ipfs/ipfs

The backstory to decentralised web of nodes proposition (or most things) - which makes sense of what he is proposing and why it will work:

https://www.youtube.com/watch?v=Fa4pckodM9g

edit



With nodes: more decentralized nodes, the faster the download speeds.

With http: the more the users, the slower the download speeds.

Simples,

http://academictorrents.com/
At syncing, the download speed is irrelevant, the hard work for the wallet is to process the incoming data (checkblock: verify hash, verify data, etc)


Well, I wouldn't say that download speed is irrelevant, but the bottleneck of synching a full node is definitely the CPU.

Also, if I am not mistaken (I am not sure how Core does it), a full node will always download a single block, then validate it, then ask and wait for the next block to download, validate again etc...
A very serial process.
While the CPU is validating, the program isn't allowed to download the next block, for obvious reasons: if the last block is false, all following blocks are also false (wrong fork).
But not being allowed to download further blocks is what makes synching even slower.

(And vice versa, while the next block is still downloading, the CPU can't validate yet. All those waiting times add to a large delay, especially when you consider hundreds of thousands of blocks.)

So is this the best way of doing things?

The goal is to have better initial synching speed. It concerns people who download a blockchain from scratch, or need to sync weeks or months of data.

It can be argued that syncing could be much faster by downloading a large chunk of the longest available blockchain once (servicenodes will help out), and then do the initial validation process in one sweep,
and if there are errors, go back to serial processing as it is done now--> validate and download the rest of the blockchain from the last validated index, block by block.

Serial processing is necessary once your wallet is up-to-date (or near up-to-date), and you just need to keep track of the best blockchain available on a per-minute basis.
But is it necessary for the initial sync process, that is the question....

legendary
Activity: 1456
Merit: 1000
...At syncing, the download speed is irrelevant, the hard work for the wallet is to process the incoming data (checkblock: verify hash, verify data, etc)


I hadn't really factored that it. Thanks.

I was actually thinking about how you could use a decentralized web to authenticate on the fly login requests. Where do the credentials go, how do they get stored, etc?

Do you create a docker container, let the user pull down a run application request, run the application for a session, authenticate (against what?), then allow the user access to xyz. Does the application issue a public key to the user, and matches the return of the public key with the users issued public key to initiate a session now involving private keys?  

edit

Been for a walk to think about this, and maybe its achievable - well in theory.

* There is a live demo of github repo being pulled into a decentralized environment.
* Protonmail has demonstrated the use of emails using public keys as the initiators of an anonymous and encrypted communication session between two users (user and application, in this example)
* Decentralized web is evidently possible, with live working examples
* Randomly selected ServiceNodes can facilitate and connect all the above

* What this needs are one time issued passwords -> user initiated pull from decentralized github to run a bat file on a servicenode which generates a password and issues it to the user, after entering into anonymous communications with the user through public keys

* the user gets a second layer of protection when initiating a communication 'transaction' by using mobile 2FA against their private keys - two stage login process to prevent sybil attacks.

Don't know why it hasn't been done already, duh  Tongue

edit edit

or maybe just use Trezor for password less logins, lol

http://cointelegraph.com/news/114456/trezor-offers-password-less-login-to-other-websites-adds-dash
hero member
Activity: 525
Merit: 531
Building decentralized web on nodes - interesting

https://youtu.be/999q3_htKPU?t=8m58s

edit

https://github.com/ipfs/ipfs

The backstory to decentralised web of nodes proposition (or most things) - which makes sense of what he is proposing and why it will work:

https://www.youtube.com/watch?v=Fa4pckodM9g

edit



With nodes: more decentralized nodes, the faster the download speeds.

With http: the more the users, the slower the download speeds.

Simples,

http://academictorrents.com/
At syncing, the download speed is irrelevant, the hard work for the wallet is to process the incoming data (checkblock: verify hash, verify data, etc)
full member
Activity: 140
Merit: 100
Building decentralized web on nodes - interesting

https://youtu.be/999q3_htKPU?t=8m58s

edit

https://github.com/ipfs/ipfs

The backstory to decentralised web of nodes proposition (or most things) - which makes sense of what he is proposing and why it will work:

https://www.youtube.com/watch?v=Fa4pckodM9g

edit



With nodes: more decentralized nodes, the faster the download speeds.

With http: the more the users, the slower the download speeds.

Simples,

http://academictorrents.com/


let me check it out
legendary
Activity: 1526
Merit: 1001
Crypto since 2014
Hey guys I stumbled into this:


What the hell. You can at least provide a reason or something.

They don't like fud and criticism.. should ask yourself why
Did sparkster FUD or anything? Maybe an ip issue.
legendary
Activity: 1526
Merit: 1001
Crypto since 2014
Quote from: MrSpace link=topic=1045373.msg11521095#msg11521095
MrSpace, I would just like to know what I did for you to be like this.
I can't think of anything.

MOTOcoin !
What about it?

The developers left and the website has expired and no one on there talks. How is that my fault?
newbie
Activity: 56
Merit: 0
Quote from: MrSpace link=topic=1045373.msg11521095#msg11521095
MrSpace, I would just like to know what I did for you to be like this.
I can't think of anything.

MOTOcoin !
legendary
Activity: 1526
Merit: 1001
Crypto since 2014
Quote from: MrSpace link=topic=1045373.msg11521095#msg11521095
MrSpace, I would just like to know what I did for you to be like this.
I can't think of anything.
newbie
Activity: 56
Merit: 0
in the long run im thinking that we need a kind of API and a extra layer for communications between nodes, and services, then it would be possible to implement whatever services people would want, and the node owners could pick whatever extra services they would like to run.... but alas, this is in the future

I was thinking along the same lines.

First we need to create fix hardcoded services so that we can gather experience and knowledge, and get the project started. (full node service, decentralized messaging, decentralized domain service maybe?, decentralized search engine, github, forum, etc, etc,...)

But while we are doing that, keep in mind that the end goal would always be to create an environment that is capable to run one last service that allows you to create your own services, in a modular way.
This final service will then also replace all previous services because they can now be emulated.

Something like this music program I use, that lets you create your own synthesizers thru a modular node-based system, where you are allowed to connect all kinds of moduls thru signals and slots.

http://i.imgur.com/7MgAGwz.gif

Something like that but with crypto related moduls and dependencies ---> revolution!!!

Bump....for end of road, road map


http://i.imgur.com/H99kzci.jpg?1

End of the road, now to start on that sand path  Grin
legendary
Activity: 1456
Merit: 1000
in the long run im thinking that we need a kind of API and a extra layer for communications between nodes, and services, then it would be possible to implement whatever services people would want, and the node owners could pick whatever extra services they would like to run.... but alas, this is in the future

I was thinking along the same lines.

First we need to create fix hardcoded services so that we can gather experience and knowledge, and get the project started. (full node service, decentralized messaging, decentralized domain service maybe?, decentralized search engine, github, forum, etc, etc,...)

But while we are doing that, keep in mind that the end goal would always be to create an environment that is capable to run one last service that allows you to create your own services, in a modular way.
This final service will then also replace all previous services because they can now be emulated.

Something like this music program I use, that lets you create your own synthesizers thru a modular node-based system, where you are allowed to connect all kinds of moduls thru signals and slots.



Something like that but with crypto related moduls and dependencies ---> revolution!!!

Bump....for end of road, road map
legendary
Activity: 1484
Merit: 1007
spreadcoin.info
vanitygen is working with uncompressed addresses.
the displayed SieiiXS9E2... address is an uncompressed address, while SSCwYC... address is the compressed (private key is VK39vRX8uy5MwaQ72ySKwV66KXyZDebGct65W3nMg69kgXf3vBL9 )
both have the same private ECDSA key (621CFB6D7AA39D2AD993F39AB560CD1A872DD68D1C22199A7E48B5F96AECE153)

you can verify it: http://www.universalwalletgenerator.net/ -> setup custom, public address: 63

Elbandi

So I managed to adjust the vanitygen so that it generates compressed addresses by borrowing from this:

https://github.com/salfter/vanitygen/commit/7ee7d9b0aa5b3841d17f0be14d2cc00f719b579f

And it works, it generates compressed SPR privkeys (starting with Letter V instead of 7 (uncompressed).

And I check the validity of the privkey on http://www.universalwalletgenerator.net/ (setup with 63,191, and then wallet-details)
and it works, it recognizes the correct SPR Vanity address.

Problem I still have is, how can I import this address into the wallet?

When I do a simple importprivkey it reports an error.

Is importprivkey as it is implemented ATM even able to import compressed keys?

Doesn't look like it.
legendary
Activity: 1358
Merit: 1002

i suspect this might have something to do with it:

in spreadcoin
// secp256k1:
// const unsigned int PRIVATE_KEY_SIZE = 279;
// const unsigned int PUBLIC_KEY_SIZE  = 33;
// const unsigned int SIGNATURE_SIZE   = 65;

in darkcoin:
// secp256k1:
// const unsigned int PRIVATE_KEY_SIZE = 279;
// const unsigned int PUBLIC_KEY_SIZE  = 65;
// const unsigned int SIGNATURE_SIZE   = 72;

 // see www.keylength.com
 // script supports up to 75 for single byte push

Now it makes sense why it is only size of 33 with spreadcoin.... ---> it's compressed!  Roll Eyes


yes, the compressed key is used all over in the source
legendary
Activity: 1456
Merit: 1000

i suspect this might have something to do with it:

in spreadcoin
// secp256k1:
// const unsigned int PRIVATE_KEY_SIZE = 279;
// const unsigned int PUBLIC_KEY_SIZE  = 33;
// const unsigned int SIGNATURE_SIZE   = 65;

in darkcoin:
// secp256k1:
// const unsigned int PRIVATE_KEY_SIZE = 279;
// const unsigned int PUBLIC_KEY_SIZE  = 65;
// const unsigned int SIGNATURE_SIZE   = 72;

 // see www.keylength.com
 // script supports up to 75 for single byte push

Now it makes sense why it is only size of 33 with spreadcoin.... ---> it's compressed!  Roll Eyes


But you can un-compress it  Tongue
legendary
Activity: 1484
Merit: 1007
spreadcoin.info

i suspect this might have something to do with it:

in spreadcoin
// secp256k1:
// const unsigned int PRIVATE_KEY_SIZE = 279;
// const unsigned int PUBLIC_KEY_SIZE  = 33;
// const unsigned int SIGNATURE_SIZE   = 65;

in darkcoin:
// secp256k1:
// const unsigned int PRIVATE_KEY_SIZE = 279;
// const unsigned int PUBLIC_KEY_SIZE  = 65;
// const unsigned int SIGNATURE_SIZE   = 72;

 // see www.keylength.com
 // script supports up to 75 for single byte push

Now it makes sense why it is only size of 33 with spreadcoin.... ---> it's compressed!  Roll Eyes
legendary
Activity: 1504
Merit: 1002
Have you ever thought I am Mr. Spread ?


LMFAO - There is no way in all that is holy that you are Mr. Spread.  Mr. Spread had class, self control, and smarts.  You sir are lacking in all three.  You do serve a purpose though.

- pokeytex
legendary
Activity: 2870
Merit: 1091
--- ChainWorks Industries ---
So the program gives me a result after a second:

Code:
Address: SieiiXS9E2Gc22AtmAnzGXFpjGr1VbokaG
Privkey: 7R2PsAdjaJEgBZ34dhRmcuanABeHMzTLrN6EFjmiPT69zXyFUJi

But after I import this privkey into my wallet (doesn't matter if it's the old or new wallet)....

Code:
importprivkey 7R2PsAdjaJEgBZ34dhRmcuanABeHMzTLrN6EFjmiPT69zXyFUJi SOMELABEL false

....it does import the privkey alright, but it's from a totally different address:

SSCwYCKryr2gSLxuyDaCxCRGtangqxLfSi
vanitygen is working with uncompressed addresses.
the displayed SieiiXS9E2... address is an uncompressed address, while SSCwYC... address is the compressed (private key is VK39vRX8uy5MwaQ72ySKwV66KXyZDebGct65W3nMg69kgXf3vBL9 )
both have the same private ECDSA key (621CFB6D7AA39D2AD993F39AB560CD1A872DD68D1C22199A7E48B5F96AECE153)

you can verify it: http://www.universalwalletgenerator.net/ -> setup custom, public address: 63

Elbandi

what is the use of a vanity address? ...

i mean - that really doesnt have any real bearing on spr itself and the project as a whole does it? ...

or am i missing something obvious here? ...

#crysx

Thanks to elbandi for explaining this.

That's the reason I do the vanitygen, it forces me to explore everything about spreadcoin step by step.


o ok ... kool ...

i honestly thought it was something that was integral and highly important to the coin and wallet and all things spr ...

its not ... but your involvement within the development arena is - so all good mate and happy exploration Smiley ...

#crysx
legendary
Activity: 1484
Merit: 1007
spreadcoin.info
So the program gives me a result after a second:

Code:
Address: SieiiXS9E2Gc22AtmAnzGXFpjGr1VbokaG
Privkey: 7R2PsAdjaJEgBZ34dhRmcuanABeHMzTLrN6EFjmiPT69zXyFUJi

But after I import this privkey into my wallet (doesn't matter if it's the old or new wallet)....

Code:
importprivkey 7R2PsAdjaJEgBZ34dhRmcuanABeHMzTLrN6EFjmiPT69zXyFUJi SOMELABEL false

....it does import the privkey alright, but it's from a totally different address:

SSCwYCKryr2gSLxuyDaCxCRGtangqxLfSi
vanitygen is working with uncompressed addresses.
the displayed SieiiXS9E2... address is an uncompressed address, while SSCwYC... address is the compressed (private key is VK39vRX8uy5MwaQ72ySKwV66KXyZDebGct65W3nMg69kgXf3vBL9 )
both have the same private ECDSA key (621CFB6D7AA39D2AD993F39AB560CD1A872DD68D1C22199A7E48B5F96AECE153)

you can verify it: http://www.universalwalletgenerator.net/ -> setup custom, public address: 63

Elbandi

what is the use of a vanity address? ...

i mean - that really doesnt have any real bearing on spr itself and the project as a whole does it? ...

or am i missing something obvious here? ...

#crysx

Thanks to elbandi for explaining this.

That's the reason I do the vanitygen, it forces me to explore everything about spreadcoin step by step.
legendary
Activity: 1456
Merit: 1000
Building decentralized web on nodes - interesting

https://youtu.be/999q3_htKPU?t=8m58s

edit

https://github.com/ipfs/ipfs

The backstory to decentralised web of nodes proposition (or most things) - which makes sense of what he is proposing and why it will work:

https://www.youtube.com/watch?v=Fa4pckodM9g

edit



With nodes: more decentralized nodes, the faster the download speeds.

With http: the more the users, the slower the download speeds.

Simples,

http://academictorrents.com/

legendary
Activity: 2254
Merit: 1278
Only slightly off-topic (there's a comment from the Maidsafe folk), rumblings about PM David Cameron and Home Secretary Theresa May's intentions to backdoor all UK-sourced cryptography:

“Escaping the May-trix: Snoopers’ Charter will force a mass exodus of tech firms from the UK”
http://www.thenational.scot/news/escaping-the-may-trix-snoopers-charter-will-force-a-mass-exodus-of-tech-firms-from-the-uk.3636


but the illustration is absolutely priceless:



Cheers

Graham

legendary
Activity: 1694
Merit: 1002
Decentralize Everything
Jump to: