Topic: [ANN] SpreadCoin | Decentralize Everything (decentralized blockexplorer coming) - page 188. (Read 790391 times)
January 20, 2016, 05:27:10 PM
I don't know if anyone mentioned it already, but could the exchange https://c-cex.com/ be anything for SPR? I am not familiar with the exchange myself...
January 20, 2016, 05:02:19 PM
January 20, 2016, 01:07:21 PM
 |  | Decentralized Blockexplorer Competitive collateral servicenodes each running a UBA module will enable spreadcoin's first decentralized service: A decentralized blockexplorer operating from within the spreadcoin wallet, allowing servicenodes to host any coin they like. The ongoing "Altcoin Taxonomy Project" and its implementation of coinURIs will create the largest best reviewed database of altcoins, encouraging a more informed decision-making among both users and servicenode operators. | |
 | | Anonymous & Decentralized Big Data Methodology Big Data done the wrong way can pose a great danger to both privacy and decentralization. Therefor preliminary research is currently done to explore privacy, security and validity issues. Note that the potential monetization and profitability of Big Data is completely irrelevant at this stage. It is entirely possible that Big Data will turn out to be incompatible with true decentralization principles, in which case we will limit the use of all analyzed network data to merely improve the operation of servicenodes. | |
 | | Proof Of Bitcoin Node / Proof Of Any Node Proving that a full bitcoin node is exclusively installed and used by a single servicenode requires a solution similar in complexity and about as groundbreaking as solving the double-spend problem in bitcoin. Solving PoBN will likely allow the creation of a decentralized exchange and (should a valid big data methodology be found) a big data market. |
January 20, 2016, 11:08:44 AM
So, UNA and UBA?
 | | UBA stands for Universal Blockchain Analyzer. It's a built-in module that specializes in reading other coins blockchain data. It creates indexed and secured datastructures that are optimized for their distribution over the servicenodes network to be used for the decentralized blockexplorer | |
 | | UNA stands for Universal Network Analyzer. Once we have agreed on a methodoly for anonymous and decentralized big data, we will start development of another built-in module that scans network traffic caused by the hosted daemons. We will leave the daemons alone and not use their RPC services to ask them for info, we will rather deduce any info from the network streams themselves. |
January 20, 2016, 07:24:15 AM
So, UNA and UBA?
January 20, 2016, 07:01:25 AM
...
pretty scary graphs!
pretty scary graphs!
We might have to invent a new term for Big Data.....maybe Huge Motherf***ing Data?
January 20, 2016, 06:35:15 AM
It will grow even faster once the blocksize limited is eg. set to 2 MB.
It currently hits the 1 MB blocksize limit from time to time ...
So in a few years 2 MB times 144 blocks a day = 288 MB up to ~ 100GB growth a year
It currently hits the 1 MB blocksize limit from time to time ...
So in a few years 2 MB times 144 blocks a day = 288 MB up to ~ 100GB growth a year
It looks like your figures correlate to the 5% growth rate chart?
I've just realised how important this project is to me:
pretty scary graphs!
January 20, 2016, 06:00:56 AM
It will grow even faster once the blocksize limited is eg. set to 2 MB.
It currently hits the 1 MB blocksize limit from time to time ...
So in a few years 2 MB times 144 blocks a day = 288 MB up to ~ 100GB growth a year
It currently hits the 1 MB blocksize limit from time to time ...
So in a few years 2 MB times 144 blocks a day = 288 MB up to ~ 100GB growth a year
It looks like your figures correlate to the 5% growth rate chart?
I've just realised how important this project is to me:
January 19, 2016, 09:46:49 PM
It will grow even faster once the blocksize limited is eg. set to 2 MB.
It currently hits the 1 MB blocksize limit from time to time ...
So in a few years 2 MB times 144 blocks a day = 288 MB up to ~ 100GB growth a year
It currently hits the 1 MB blocksize limit from time to time ...
So in a few years 2 MB times 144 blocks a day = 288 MB up to ~ 100GB growth a year
It looks like your figures correlate to the 5% growth rate chart?
January 19, 2016, 09:08:06 PM
It will grow even faster once the blocksize limited is eg. set to 2 MB.
It currently hits the 1 MB blocksize limit from time to time ...
So in a few years 2 MB times 144 blocks a day = 288 MB up to ~ 100GB growth a year
It currently hits the 1 MB blocksize limit from time to time ...
So in a few years 2 MB times 144 blocks a day = 288 MB up to ~ 100GB growth a year
January 19, 2016, 08:02:33 PM
How Blockchain.info see the actual historic growth of the Bitcoin block chain. See the recent acceleration in recently years? Looks more like the 5% is the right growth rate trend.
btw, this is Big Data in action
btw, this is Big Data in action
January 19, 2016, 07:52:56 PM
...but, if you actually use a 5% growth rate, you get this:
Tell me that Bitcoin won't need VPS hosted full nodes within the next few years....going on, I dare you.
edit
I was just trying to figure out how much bandwidth would be required in three years time, with around 15GB per month circulating between 3,000 to 5,000 SPR full Bitcoin nodes, plus between our bitcoin nodes and millions of SPVs and I think I broke my spreadsheet. It's TBs and TBs of data.
Tell me that Bitcoin won't need VPS hosted full nodes within the next few years....going on, I dare you.
edit
I was just trying to figure out how much bandwidth would be required in three years time, with around 15GB per month circulating between 3,000 to 5,000 SPR full Bitcoin nodes, plus between our bitcoin nodes and millions of SPVs and I think I broke my spreadsheet. It's TBs and TBs of data.
January 19, 2016, 07:49:30 PM
So I ran some numbers on the growth of Bitcoin's block chain, for full nodes.
The current monthly growth rate is 5%. So I decided to see what it would look like with 3%, over the next three years (new project business plans tend to be based on three year projections).
edit
changed title
The current monthly growth rate is 5%. So I decided to see what it would look like with 3%, over the next three years (new project business plans tend to be based on three year projections).
edit
changed title
January 19, 2016, 07:34:03 PM
This is a good business plan, and seems to be getting better. I've invested some considerable amount into it. I cannot recommend however hosting anything with teamviewer as a method of controlling it. I had set up a vutr account with a windows OS, and got hacked for 56k spr (in august, when it was worth much less). This can be seen at the "johnpadalecki" account registered then. This has apparently happened recently to another member, through the same apparatus. Beware teamviewer. I am still using it, but using all different paswords on each computer. And a completely isolated email account.
Did you use a very weak teamviewer password?
I read about that a few times now. Here an older one:
The hacker is straight after your wallet dats (appdata/roaming)
https://www.reddit.com/r/hacking/comments/291525/someone_accessed_my_computer_through_teamviewer/
January 19, 2016, 07:29:59 PM
So the difference between your project and mine is:
Yours is a giant database regarding the "Description of a Cryptocurrency".
While the "altcoin taxonomy" project is about giving coins a unique collision-free identifier (coinURI), derived simply by reading its blockchain.
The goal is to tie the "blockchain of a coin" to the "design of a coin" (what is in DOACC) with the use of those coinURIs.
Yours is a giant database regarding the "Description of a Cryptocurrency".
While the "altcoin taxonomy" project is about giving coins a unique collision-free identifier (coinURI), derived simply by reading its blockchain.
The goal is to tie the "blockchain of a coin" to the "design of a coin" (what is in DOACC) with the use of those coinURIs.
I thought you might be able to re-use the DOACC coinURIs but I was mistaken.
Cheers
Graham
But if you were to add spreadcoin's coinURIs to your DOACC then we could reuse ALL your data within the blockexplorer.
These coinURIs could be the bridge between blockchains and our databases so to speak.
Currently, for our project, we are going with a combination of the 4 magic bytes of a coin's blockchain and the 4 bytes of the timecode of the genesis block's creation.
This leads for example to the following coinURIs:
Spreadcoin = 4f3c5cbb53d75160
Bitcoin = f9beb4d9495fab29
Dash = bf0c6bbd52db2d02
Litecoin = fbc0b6db4e8eaab9
We still need to process more coins, just to be 100% sure that there are no collisions between different coins. But it looks good so far!
Think of it this way: we are creating a standard ID (coinURI) that isn't awarded by a human being, but that can simply be deduced from a coins blockchain (Magicbytes + time) even by a machine.
This coinURI then serves as a key we can use in a database to search for the correlating coin specification/description.
Only requirement would be that available databases start adapting coinURIs.
BTW: nice sideeffect of adding coinURIs to your database is that it immediately adds knowledge to it (magicbytes and when the coin's genesisblock was created, you just need to convert hex to unix timestamp)
January 19, 2016, 06:25:44 PM
So the difference between your project and mine is:
Yours is a giant database regarding the "Description of a Cryptocurrency".
While the "altcoin taxonomy" project is about giving coins a unique collision-free identifier (coinURI), derived simply by reading its blockchain.
The goal is to tie the "blockchain of a coin" to the "design of a coin" (what is in DOACC) with the use of those coinURIs.
Yours is a giant database regarding the "Description of a Cryptocurrency".
While the "altcoin taxonomy" project is about giving coins a unique collision-free identifier (coinURI), derived simply by reading its blockchain.
The goal is to tie the "blockchain of a coin" to the "design of a coin" (what is in DOACC) with the use of those coinURIs.
I thought you might be able to re-use the DOACC coinURIs but I was mistaken.
Cheers
Graham
January 19, 2016, 06:20:55 PM
Interesting, the bitcoin blockchain is now 56GB, and picking up its growth rate
https://blockchain.info/charts/blocks-size?showDataPoints=true&show_header=true&daysAverageString=7×pan=all&scale=0&address=
https://blockchain.info/charts/blocks-size?showDataPoints=true&show_header=true&daysAverageString=7×pan=all&scale=0&address=
January 19, 2016, 04:22:10 PM
I did earlier, that's why I posted.
If you haven't read it already:
DOACC docs, https://doacc.github.io/
Cheers
Graham
Thanks, I'll look into it.
So the difference between your project and mine is:
Yours is a giant database regarding the "Description of a Cryptocurrency".
While the "altcoin taxonomy" project is about giving coins a unique collision-free identifier (coinURI), derived simply by reading its blockchain.
The goal is to tie the "blockchain of a coin" to the "design of a coin" (what is in DOACC) with the use of those coinURIs.
January 19, 2016, 04:10:52 PM
I did earlier, that's why I posted.
If you haven't read it already:
DOACC docs, https://doacc.github.io/
Cheers
Graham
January 19, 2016, 04:00:20 PM
Awesome, I'll add the info everywhere.
Jump to: