Topic: Sia - Siafund Redemption Deadline: June 1st, 2015 - page 15. (Read 68779 times)
Will Nebulous issue stocks in the near future? Will siastocks have a chance to convert to Nebulous stocks?
We're thinking 3.9%. If we took too much, then hosts wouldn't be inclined to be on our network, which would be bad for the entire network.
The Siastock would be owned by Nebulous Incorporated, which is a company and not two individuals. That's an important distinction. We are looking for large volumes of income, initially on the order of millions of dollars but we would like to see Nebulous become a Google or Microsoft sized company. At that point most of the revenue would be coming from sources other than Siastock, of course.
The big reason we're looking at taking a lot of money is so that we can do a lot with the cryptocurrency. Bitcoin is often criticized as being underfunded. Imagine if Satoshi's 1 million btc were funding a corporation with hundreds of full time developers, marketing, and actively doing things like attacking mastercard. That's where our Siastock will be going.
The Siastock would be owned by Nebulous Incorporated, which is a company and not two individuals. That's an important distinction. We are looking for large volumes of income, initially on the order of millions of dollars but we would like to see Nebulous become a Google or Microsoft sized company. At that point most of the revenue would be coming from sources other than Siastock, of course.
The big reason we're looking at taking a lot of money is so that we can do a lot with the cryptocurrency. Bitcoin is often criticized as being underfunded. Imagine if Satoshi's 1 million btc were funding a corporation with hundreds of full time developers, marketing, and actively doing things like attacking mastercard. That's where our Siastock will be going.
On Sia's website under Sianotes (http://www.siacoin.com/sianotes.html) it says that "the developers will own the majority of Siastock". I know there are only 1250 sianotes in circulation which represents a little under 0.5% of host income. Sia is tentatively planning on having a 3.9% fee so does this mean the remaining 8,750 sianotes, which represents a little more than 3.4% of host income, is held by the developers? Or are the remaining sianotes just not in circulation and no one has them yet? I'm fine with the developers keeping sianotes because they should be able to reward themselves for all the work. I'm just wondering how much they have because I think at some point it could potentially be too much. Thanks for explaining!
From my understand the devs hold the rest unless they have another ipo and then it will get distributed again.
On Sia's website under Sianotes (http://www.siacoin.com/sianotes.html) it says that "the developers will own the majority of Siastock". I know there are only 1250 sianotes in circulation which represents a little under 0.5% of host income. Sia is tentatively planning on having a 3.9% fee so does this mean the remaining 8,750 sianotes, which represents a little more than 3.4% of host income, is held by the developers? Or are the remaining sianotes just not in circulation and no one has them yet? I'm fine with the developers keeping sianotes because they should be able to reward themselves for all the work. I'm just wondering how much they have because I think at some point it could potentially be too much. Thanks for explaining!
We've already been in touch with storj. We're both looking at working together but it's difficult to tell how exactly to fit the pieces together. We're also in the next few months going to be looking at joining forces with other Boston based cryptocurrencies, and we'll definitely be involved with the MIT Bitcoin project.
Right now most alt-coins are competing with each other. I think there's some room to change that to at least some degree, but the biggest obstacle is that everyone is so passionate about what they're currently working on. But right now the politics are very friendly, and we might get some very powerful partnerships up and running in the next year or so.
====
In other news, I've been looking at our current automatic repair scheme for files, and I've realized that repairing low redundancy files is extremely expensive using Reed-Solomon encoding, even if you wait until you're repairing 8-12 files at a time. As an only solution, I don't think it's reasonable.
Luckily we've got a large array of options available to us. We can have a slow-degrade of files, where when 1 node goes offline all the other nodes respond by shifting some of their data to the new node. You start with a file at 1.2 or 1.5 redundancy (or whatever), and over time it slowly degrades to 1 and less than 1 redundancy as nodes fail. It's then up to you to figure out when to repair it. This is obviously not ideal because then the network can't automatically repair your files, but it might not be difficult to set up some sort of peripheral service (perhaps even a decentralized peripheral service) that automatically repairs your files for you as they degrade. And maybe we could establish some rules for extending redundancy and... anyway, it's an option that's available to us.
Another option is to support other types of codes. Reed-Solomon codes are nice because they're maximum-distance separable. A redundancy of 3 results in storing 3 complete copies of the file. A redundancy of 1.2 results in storing 1.2 complete copies of the file. LT codes, Spinal codes, and Raptor codes are all alternatives that might be cheaper to repair, but you lose the some efficiency in storage. A redundancy of 3 might take 3.5 or 5 complete copies of the file being stored. But if you can repair files using only 50% extra bandwidth instead of 15000% extra bandwidth, it could be worth the tradeoff.
What I'm really going to be holding out for, and perhaps working on myself (once the other facets of Sia are developed, so don't expect anything soon), is a new type of erasure code that is both maximum-distance separable and minimum-bandwidth recoverable. That means that repairing a 16MB file piece would only take 16MB of downloads, instead of needing to rebuild the entire original file that the pieces build out. Intuitively, it seems possible. I have no idea, but I'm not aware of any mathematical laws indicating that it wouldn't be possible.
Regardless, this ultimately means that automatic file repairing is not going to be a feature for a while. We'll be working on the other pieces of quorum-based cryptocurrency and giving the expensive recovery problem time to stew. I'm optimistic for the long term prospects.
Right now most alt-coins are competing with each other. I think there's some room to change that to at least some degree, but the biggest obstacle is that everyone is so passionate about what they're currently working on. But right now the politics are very friendly, and we might get some very powerful partnerships up and running in the next year or so.
====
In other news, I've been looking at our current automatic repair scheme for files, and I've realized that repairing low redundancy files is extremely expensive using Reed-Solomon encoding, even if you wait until you're repairing 8-12 files at a time. As an only solution, I don't think it's reasonable.
Luckily we've got a large array of options available to us. We can have a slow-degrade of files, where when 1 node goes offline all the other nodes respond by shifting some of their data to the new node. You start with a file at 1.2 or 1.5 redundancy (or whatever), and over time it slowly degrades to 1 and less than 1 redundancy as nodes fail. It's then up to you to figure out when to repair it. This is obviously not ideal because then the network can't automatically repair your files, but it might not be difficult to set up some sort of peripheral service (perhaps even a decentralized peripheral service) that automatically repairs your files for you as they degrade. And maybe we could establish some rules for extending redundancy and... anyway, it's an option that's available to us.
Another option is to support other types of codes. Reed-Solomon codes are nice because they're maximum-distance separable. A redundancy of 3 results in storing 3 complete copies of the file. A redundancy of 1.2 results in storing 1.2 complete copies of the file. LT codes, Spinal codes, and Raptor codes are all alternatives that might be cheaper to repair, but you lose the some efficiency in storage. A redundancy of 3 might take 3.5 or 5 complete copies of the file being stored. But if you can repair files using only 50% extra bandwidth instead of 15000% extra bandwidth, it could be worth the tradeoff.
What I'm really going to be holding out for, and perhaps working on myself (once the other facets of Sia are developed, so don't expect anything soon), is a new type of erasure code that is both maximum-distance separable and minimum-bandwidth recoverable. That means that repairing a 16MB file piece would only take 16MB of downloads, instead of needing to rebuild the entire original file that the pieces build out. Intuitively, it seems possible. I have no idea, but I'm not aware of any mathematical laws indicating that it wouldn't be possible.
Regardless, this ultimately means that automatic file repairing is not going to be a feature for a while. We'll be working on the other pieces of quorum-based cryptocurrency and giving the expensive recovery problem time to stew. I'm optimistic for the long term prospects.
do you think you are able to join forces with storj? i think one decentralized cloud storage is enough,
then we can develop all the other decentalized apps based on storage
then we can develop all the other decentalized apps based on storage
It seems that Sianotes price has increased more than 30% in term of Nxt and 100% in term of BTC. https://nxtblocks.info/#section/assets_exchange/11593659039925686857
Typical for an alpha release. Expect much bigger returns when Sia is up and running.
It seems that Sianotes price has increased more than 30% in term of Nxt and 100% in term of BTC. https://nxtblocks.info/#section/assets_exchange/11593659039925686857
Thanks for the update!
The first alpha release is complete. This isn't intended to be used for actual file storage, just to demonstrate what Sia might look like. Feedback is appreciated, but we are aware of a large number of bugs and points of insecurity. There's a lot that hasn't been implemented yet. Think of it more as a proof-of-concept than a traditional alpha.
Check it out at siacoin.com/download.html
There you will find an explanation on how to download and install Sia. Unfortunately, we don't have Windows binaries yet.
We have an IRC channel now, #sia-talk on freenode. We have registered a few other channels for future use, but until there's a need for them we plan on keeping them mostly dormant.
Things you can do with the current alpha:
Create wallets
Send money between wallets
Upload files to wallets (max 256 atoms, explained later)
Download files
The block speed for the alpha release is 256 seconds per block. Unfortunately, many actions such as upload take several blocks to complete, though never more than 4. This can make the production Sia a little slow to play around with. (If it really bothers you, you can recompile with a shorter interval.) The full version of Sia will have block speeds somewhere between 1 block every 2-16 hours. However, it will also support accelerated actions, which can only occur under certain but easily achieved constraints. Most people will not realize that Sia moves at a pace of 1 step every few hours, because they will be using cryptographic proofs behind the scenes to accelerate their actions. These accelerations won't be supported in Sia until the beta.
Notes:
- Empty wallets do not get deleted.
- Participants do not get kicked for not having files.
- Participants do get kicked for missing a single heartbeat. This can cause problems for unstable connections
- Sometimes participants don't join the quorum in-sync. This is rare, and the fix is to just try again.
- After creating a new quorum, you must wait a full block before adding any siblings.
- You may encounter some hard crashes. This is because a good error-handling framework is still in the works.
What are Atoms?
An atom is a unit of storage on the Sia network. Uploaders are allowed to pick their own redundancy, which means that the amount of data which can be stored in an atom is variable. At full redundancy (every sibling has the complete file), only 4kb can be stored per atom, the max file size is 1MB, and the redundancy is equal to the quorum size. (For the alpha, the quorum size is 32). At a lower redundancy (like double redundancy), an atom is 4KB * 16 hosts, which means the max file size is slightly more flexible.
Picking a Redundancy
Redundancy works by picking a value, k, which represents the number of siblings that need to remain online in order for the file to be recoverable. The amount of redundancy is QuorumSize/K. At k=32 (the current quorum size), the redundancy is 1, meaning there is exactly 1 copy of the file on the network. At k=16, there are 2 complete copies of the file on the network, and the original file can be rebuilt from any 16 siblings.
Setting up a Quorum
Right now, all quorums are pseudo-decentralized, which means that anybody can establish a quorum, and anybody can join a quorum that has extra space for siblings. To establish a quorum, run the server executable and type 'e'. This creates a new quorum bootstrapped to your current address and chosen port number. To join a quorum, type 'j', and input the address of any host in the quorum you wish to join.
Messing Around
Feel free to dig into the source code a bit. To reduce the quorum size (which reduces the block speed), change QuorumSize in src/quorum/quorum.go. To change the step length (currently set to 8 seconds, reducing this will also reduce the block speed), change StepDuration in src/participant/listen.go.
We realize right now that setting up a quorum is a bit of a pain, and that there are lots of frustrating things that can go wrong while keeping one running. This is merely a result of the early stage of the software. Later versions will be easier to use, less dependent on a stable internet connection, and will not have occasional synchronization hiccups.
Moving Forward:
The first thing we're doing is taking a 3-4 day break from coding. It's easy to get your head buried and miss out on what's happening in the rest of the world. We'll be using this time to take a broader perspective on Sia and figure out what the next best steps are.
We're also setting a deadline for a alpha v2 release in 3-4 weeks. This alpha will have:
+ increased DOS (denial-of-service) protection
+ automatic port forwarding
+ smooth, cryptographic synchronization among hosts
+ wallets that get deleted upon running out of money
+ nonces for transactions, meaning a signed transaction can only be used once
+ proof-of-storage with cheating protection and auto-cheating implemented. (Auto cheating is something you do if you don't have the file, for example if your disk corrupts.
After that we'll be looking toward building the meta-quorums, cryptographic DOS protection (
), an instant-transaction network, and a more comfortable scripting environment.
If you have questions, you can post here, chat with us in the IRC channel, or shoot us an email.
Check it out at siacoin.com/download.html
There you will find an explanation on how to download and install Sia. Unfortunately, we don't have Windows binaries yet.
We have an IRC channel now, #sia-talk on freenode. We have registered a few other channels for future use, but until there's a need for them we plan on keeping them mostly dormant.
Things you can do with the current alpha:
Create wallets
Send money between wallets
Upload files to wallets (max 256 atoms, explained later)
Download files
The block speed for the alpha release is 256 seconds per block. Unfortunately, many actions such as upload take several blocks to complete, though never more than 4. This can make the production Sia a little slow to play around with. (If it really bothers you, you can recompile with a shorter interval.) The full version of Sia will have block speeds somewhere between 1 block every 2-16 hours. However, it will also support accelerated actions, which can only occur under certain but easily achieved constraints. Most people will not realize that Sia moves at a pace of 1 step every few hours, because they will be using cryptographic proofs behind the scenes to accelerate their actions. These accelerations won't be supported in Sia until the beta.
Notes:
- Empty wallets do not get deleted.
- Participants do not get kicked for not having files.
- Participants do get kicked for missing a single heartbeat. This can cause problems for unstable connections
- Sometimes participants don't join the quorum in-sync. This is rare, and the fix is to just try again.
- After creating a new quorum, you must wait a full block before adding any siblings.
- You may encounter some hard crashes. This is because a good error-handling framework is still in the works.
What are Atoms?
An atom is a unit of storage on the Sia network. Uploaders are allowed to pick their own redundancy, which means that the amount of data which can be stored in an atom is variable. At full redundancy (every sibling has the complete file), only 4kb can be stored per atom, the max file size is 1MB, and the redundancy is equal to the quorum size. (For the alpha, the quorum size is 32). At a lower redundancy (like double redundancy), an atom is 4KB * 16 hosts, which means the max file size is slightly more flexible.
Picking a Redundancy
Redundancy works by picking a value, k, which represents the number of siblings that need to remain online in order for the file to be recoverable. The amount of redundancy is QuorumSize/K. At k=32 (the current quorum size), the redundancy is 1, meaning there is exactly 1 copy of the file on the network. At k=16, there are 2 complete copies of the file on the network, and the original file can be rebuilt from any 16 siblings.
Setting up a Quorum
Right now, all quorums are pseudo-decentralized, which means that anybody can establish a quorum, and anybody can join a quorum that has extra space for siblings. To establish a quorum, run the server executable and type 'e'. This creates a new quorum bootstrapped to your current address and chosen port number. To join a quorum, type 'j', and input the address of any host in the quorum you wish to join.
Messing Around
Feel free to dig into the source code a bit. To reduce the quorum size (which reduces the block speed), change QuorumSize in src/quorum/quorum.go. To change the step length (currently set to 8 seconds, reducing this will also reduce the block speed), change StepDuration in src/participant/listen.go.
We realize right now that setting up a quorum is a bit of a pain, and that there are lots of frustrating things that can go wrong while keeping one running. This is merely a result of the early stage of the software. Later versions will be easier to use, less dependent on a stable internet connection, and will not have occasional synchronization hiccups.
Moving Forward:
The first thing we're doing is taking a 3-4 day break from coding. It's easy to get your head buried and miss out on what's happening in the rest of the world. We'll be using this time to take a broader perspective on Sia and figure out what the next best steps are.
We're also setting a deadline for a alpha v2 release in 3-4 weeks. This alpha will have:
+ increased DOS (denial-of-service) protection
+ automatic port forwarding
+ smooth, cryptographic synchronization among hosts
+ wallets that get deleted upon running out of money
+ nonces for transactions, meaning a signed transaction can only be used once
+ proof-of-storage with cheating protection and auto-cheating implemented. (Auto cheating is something you do if you don't have the file, for example if your disk corrupts.
After that we'll be looking toward building the meta-quorums, cryptographic DOS protection (
), an instant-transaction network, and a more comfortable scripting environment.If you have questions, you can post here, chat with us in the IRC channel, or shoot us an email.
So I wonder if there will ever be legal repercussions for the people sharing disk space for this coin.
What happens if/when a child porn ring starts using this coin to store imgs? It would mean anyone sharing disk space for this coin could possibly be arrested and tried for possessing child porn.
What happens if/when a child porn ring starts using this coin to store imgs? It would mean anyone sharing disk space for this coin could possibly be arrested and tried for possessing child porn.
If i understand this correctly there will be no way to know what do you store on your computer, it's encrypted. It will not even be full files, just pieces of data.
btw, this is a much more relevant question with some other crypto currencies
If a crypto currency allows anyone to send messages or comments what happens when someone sends the data of a child porn pic as messages, comments? Then technically anyone who stores the blochain posesses that picture.
This is why it is a very bad idea to make posession of any information or data illegal. In the near future there will be some serious problems with this.
So I wonder if there will ever be legal repercussions for the people sharing disk space for this coin.
What happens if/when a child porn ring starts using this coin to store imgs? It would mean anyone sharing disk space for this coin could possibly be arrested and tried for possessing child porn.
What happens if/when a child porn ring starts using this coin to store imgs? It would mean anyone sharing disk space for this coin could possibly be arrested and tried for possessing child porn.
Hi, we're a bit behind, but today we're working nonstop. It should be out before we go to sleep. We've got most things ready.
Thanks for the patience, sorry about the delay.
Thanks for the patience, sorry about the delay.
Take your time. Rome wasn´t build in a day, so you can take a week
Hi, we're a bit behind, but today we're working nonstop. It should be out before we go to sleep. We've got most things ready.
Thanks for the patience, sorry about the delay.
Thanks for the patience, sorry about the delay.
No worries. Take your time as long as you give an update.
Hi, we're a bit behind, but today we're working nonstop. It should be out before we go to sleep. We've got most things ready.
Thanks for the patience, sorry about the delay.
Thanks for the patience, sorry about the delay.
Hi Taek，
Is there any indication when the alpha might be out?
Is there any indication when the alpha might be out?
Will it have further IPO when it launches?
Based on what dev said, maybe and maybe not.
Will it have further IPO when it launches?
Wow crazy James from nxt has over 1/3 of the ipo shares 
Actually James bought 1/3 of the pre IPO notes and there is only about 12% of total notes was issued for the pre IPO. Overall, James asset own about 4% of total Sianotes/Siastocks. That is still huge. If Sia is taking off one day, James asset owners will be rich.
Wow crazy James from nxt has over 1/3 of the ipo shares
Jump to: