Alright, 2.0.0a1 public testing time! Compiled JAR files: http://1.curecoinmirror.com/2.0.0a1/2.0.0a1.zipSource code:Curecoin Daemon: https://github.com/Vorksholk/CurecoinCurecoin RPC Client: https://github.com/Vorksholk/CurecoinClientCurecoin Testnet Miner: https://github.com/Vorksholk/CurecoinTestnetMinerQuickstart Instructions:Launch 2.0.0a1Daemon first (Windows, double-click, any other OS enter "java -jar 2.0.0a1Daemon.jar" in the terminal, make sure you are in the directory where 2.0.0a1Daemon.jar is) Launch 2.0.0a1Client second (Windows, double-click, any other OS enter "java -jar 2.0.0a1Client.jar" in the terminal, make sure you are in the directory where 2.0.0a1Client.jar is) Launch 2.0.0a1Miner third (Windows, double-click, any other OS enter "java -jar 2.0.0a1Miner.jar" in the terminal, make sure you are in the directory where 2.0.0a1Miner.jar is) The miner does pointless hash work, it's simply to simulate doing computational work, and receiving a certificate. Certificates for mining are signed by a certificate authority server run by us, with an IP hard-coded into the miner code. It can take a few minutes to mine a block. Difficulty is fixed at 150,000. Don't make any optimized miners unless you're really bored, as the miner has no purpose other than to trickle out certificates and keep the network running with blocks. This is a TESNET release, so any Curecoins here are worthless. Each block mines 100 coins, which are atomic units (you can't send .1 of a coin). In the future, this will be the equivalent of 1 satoshi--so no need to divide them. The client comes hard-coded with one genesis block and one block after that, and then it's normally-mined blocks that the client has to catch-up with. You can type "help" in the Curecoin client to see the (very-limited, at the moment) list of commands available. |
|
|
|
Hey everyone! We got source code on a public github now! https://github.com/Vorksholk/CurecoinCheck it out! Read through the spaghetti code! Don't bother compiling anything unless you're really so-inclined, it's going to change before 2.0.0a1 public alpha, which will hopefully occur within the next 24 hours. My apologies about the code running of the screen--I'm terrible when it comes to short lines of code/comments. Not in the mood now to go through and rework my code to appear pretty on Github, but that's an eventual job to undertake. Still got some major bugs to crack, the network based on this code is very fragile. Josh broke it by sending some weird transactions. xD If you just want to scroll mindlessly through the code: https://github.com/Vorksholk/Curecoin/commit/3fb9889e57acd7a709cb5659bd07a0e52851acb4 |
|
|
|
|
While this thread is being bumped, mind as well give a 2.0 update. Internal testing of 2.0.0a1 is going great--there's one remaining bug with transaction indexes I'm chasing. Block propagation/generation, the ledger system, etc. all seem to be working well. Goal is to get a cleaned-up copy of 2.0.0a1 in public testing sometime tomorrow, June 19th. 2.0.0a1 ended up being an internal test due to tons of small tweaks and "alright, delete xyz and try again... what block are you on? What hash? Alright, try to forge a block like this..." but 2.0.0a1 should be good for a public test.
A few things to note--there are some obvious limitations of 2.0.0a1. In its current state, there is no difficulty adjustment, and for testing purposes timestamp verification is OFF. While the network protocols allow for complex transactions with multiple outputs, RPC only has a simple send command--sending to one address at a time.
For testing purposes, each block is worth 100 atomic units. Obviously in the actual client, we will have a MUCH larger block reward (in atomic units), to support many decimals (probably 8 or so) of precision. These atomic units can be thought of as micro-Curecoin. The source code will be available as a zip file and on Github. To play with the downloadable JAR, you will need Java SE 7 or 8 installed, JRE is fine.
|
|
|
|
Sent you 242 KS, thanks for maintaining that chart. |
|
|
|
do any one of you know if there is a pool or is is solo so far?
Currently solo, wolf mentioned some pool-related stuff, but if it's anywhere, it's in the super-early stages of development right now. well there is no support thread as well. or is there? I cant seem to find it. I am having an issue with mac wallet. is a good place to ask those kind of questions, as well as #siatalk on freenode.  |
|
|
|
do any one of you know if there is a pool or is is solo so far?
Currently solo, wolf mentioned some pool-related stuff, but if it's anywhere, it's in the super-early stages of development right now. |
|
|
|
Back on topic. I'm looking to buy Siacoin for .12 per 1M. I guess up to 3.5 depending, will probably only want 2 btc worth though.
Personally I think even .1 is too high. No matter how great we see the potential in Sia there could be an irreversible bug found tomorrow
that causes red headed children to explode. Otherwise nobody would even sell for less than 10 btc per 1M. But in order to
buy, buyers have to be willing to meet up to sellers and vice versa.
I will send first to members I feel fine about or you can send first. I've done escrow with anon136 a couple times so I have no
problem using him. Thats if he's even heard of Sia.
your offer is probably too low - see thisone: Looking to buy 60million sia for 0.15BTC/million. Total of 9 BTC PM if interested or with counteroffer.
Yea missed that. Still who knows if that is legit offer. i do probably have to up it though. Okay I'll go to .14 btc per 1M. For anyone interested with me if you have any kind of reputation I'll send first. That might be worth it for some. .15/mil is certainly a legit offer--I sold him 10 mil at that price. Do you have more to sell? I guess I'll match the .2 btc for 1M Siacoin. I'll buy 3 btc worth. For you I'll send first. I'm sorry, but I'm all out at that price, aside from a pending trade. I'll probably hold the remainder of my coins for a while longer, but someone in IRC might be willing to sell at .2, for anyone who mined early that is a nice price. |
|
|
|
Back on topic. I'm looking to buy Siacoin for .12 per 1M. I guess up to 3.5 depending, will probably only want 2 btc worth though.
Personally I think even .1 is too high. No matter how great we see the potential in Sia there could be an irreversible bug found tomorrow
that causes red headed children to explode. Otherwise nobody would even sell for less than 10 btc per 1M. But in order to
buy, buyers have to be willing to meet up to sellers and vice versa.
I will send first to members I feel fine about or you can send first. I've done escrow with anon136 a couple times so I have no
problem using him. Thats if he's even heard of Sia.
your offer is probably too low - see thisone: Looking to buy 60million sia for 0.15BTC/million. Total of 9 BTC PM if interested or with counteroffer.
Yea missed that. Still who knows if that is legit offer. i do probably have to up it though. Okay I'll go to .14 btc per 1M. For anyone interested with me if you have any kind of reputation I'll send first. That might be worth it for some. .15/mil is certainly a legit offer--I sold him 10 mil at that price. |
|
|
|
Wondering if anyone can shed some light on an issue I'm having:
I have 2 folding rigs setup as follows:
E3 1230v3 8gb win7x64 5x 280x all on pciex1 usb riser.
q6600 4gb win7x64 3x 280x one directly into 16x slot the other 2 running on pciex1 usb riser.
Currently I am wondering why I see such large difference in TPF for the same projects across the two rigs, for example 10467 on the E3 rig has a TPF of 5:56 compared too 10:47 on the q6600 rig. The PPD of the q6600 rig seems stupidly low considering both rigs have identical gpu. This is not the case with 9201 projects. The q6600 is running ~ 12% cpu load so that shouldn't be an issue?
The Q6600 is quite an old processor (8 years), so it may be choking PCI lanes or something. What's the GPU usage at on that box? |
|
|
|
|
Also selling, 0.12 BTC/M Sia. I'd be happy to send first in small batches.
Volume discounts:
5M+: 0.11BTC/M
10M+: 0.10BTC/M
20M+: 0.09BTC/M
Currently out of stock. Prices subject to change when I have more coins.
If I get more coins, the price will be a minimum of 0.15/M, and I'm not currently mining as EC2 isn't profitable.
|
|
|
|
That's good it will be fixed in 2.0. What is the current number of coins in circulation? Is the information currently available anywhere?
For some napkin math, we have 60673 blocks, each with a 13 CUR reward, so that's 788,749. Then we have had ~13 months of payouts, so that's 13*30*7488 = 2,920,320 That doesn't include PoS interest. Thanks. So the market cap is closer to $75,000 than the $575,000 listed on coincap.io and coinmarketcap.com. That's a big difference, I wonder what the effect has been of giving the appearance that Curecoin is valued at 8 times what it really is... To some it probably gave the impression of greater credibility and larger investments, but I imagine a 75k market cap has more upside potential than 575k. Certainly a double-edged sword, but on coinmarketcap the asterisk by the available supply denotes the large premine, so investors will know to look more into the coin composition before investing. Certainly more upside potential in 75k though |
|
|
|
That's good it will be fixed in 2.0. What is the current number of coins in circulation? Is the information currently available anywhere?
For some napkin math, we have 60673 blocks, each with a 13 CUR reward, so that's 788,749. Then we have had ~13 months of payouts, so that's 13*30*7488 = 2,920,320 That doesn't include PoS interest. |
|
|
|
So I was mining on two computers all night. I didn't mean to but I now see I was mining both on the same wallet. Now one wallet has a balance and the other still does not even though the address shows the same? Anyone tell me what happened?
When you mine a block, it adds an address to your wallet, so even though the two wallets share some addresses, any mining-related addresses created after you copied the wallet from one to the other are only stored in the wallet from the daemon that mined the block. For example, I ran EC2 instances which all had the same 'wallet' (created an AMI), but each's wallet changed once they mined a block, and each had a different balance. @Vorksholk What instance type did you use? I guess spot instances might not be good to use since the mined block will not be shared with the common wallet? I used g2 instances, spot with volumes that don't delete on shutdown (uncheck delete on termination in the storage menu when bidding). It's just a pain in the ass when instances get canceled, but you don't lose coins. |
|
|
|
So I was mining on two computers all night. I didn't mean to but I now see I was mining both on the same wallet. Now one wallet has a balance and the other still does not even though the address shows the same? Anyone tell me what happened?
When you mine a block, it adds an address to your wallet, so even though the two wallets share some addresses, any mining-related addresses created after you copied the wallet from one to the other are only stored in the wallet from the daemon that mined the block. For example, I ran EC2 instances which all had the same 'wallet' (created an AMI), but each's wallet changed once they mined a block, and each had a different balance. |
|
|
|
Is the "available supply" on coincmarketcap correct? I thought 25,000,000 is high. Is the market cap really $575,000? I personally think it should be valued at that, but I am doubtful. http://coinmarketcap.com/currencies/curecoin/I know coinmarketcap gets available supply wrong with many coins for many reasons. Is there a place to view the total number of curecoins directly? The block explorer link they post doesn't seem useful either. Yup, the they're using the full coin supply, whereas a large portion of them are held as payout premine, so they're not part of the circulation. In 2.0 the premine will be gone, so any numbers at that time will be accurate. |
|
|
|
|
Looks like Stanford's servers are having some stats reporting issues. We can't run payouts as we don't have current stats, but we will do extra proportional payouts when stats come back online--everything should be fine. Let us know if Stanford announces anything about stats servers, my head's buried in code and IRL stuff right now.
|
|
|
|
Still squashing the last few bugs before I can release the 2.0 daemon, unfortunately. I'm sure people want to see progress, so here's a zip file of the source code, with the networking code (the major headache source) over here removed, since it's gonna be completely overhauled tomorrow: http://1.curecoinmirror.com/MainProgram.zipHere's the current status: -Need networking code fixed -GUI (separate app) is bugged out -A bit more refining is needed for the blockchain storage. To launch the 2.0.0a1 daemon in a working condition, I need the networking code solid, and the blockchain storage tightened up a bit. I'm going to head off to bed as it's about 1 in the morning and I've been staring at code since morning, and I'm sure >90% of my productivity was in the first 10-ish hours of working. I have some stuff in real life to tend to tomorrow, so I'm hoping to get a daemon out by tomorrow evening, but we'll see, this morning I thought this would be a simple addition of networking code, and it seems that's just not the case. Objects in there that are broken have been replaced with some default object so they compile for other tests. And you'll notice the 2nd constructor in Block isn't finished, that's gonna take about 10 minutes to do, just don't have the brainpower to do it and test right now. |
|
|
|
I've been unable to get the miner working on a mac has anyone had better luck and can tell me what they did? I downloaded the wallet ( https://github.com/NebulousLabs/Sia-UI/releases/download/v0.3.3-beta/Sia-UI-v0.3.3-beta-darwin.tar.xz) and the miner ( https://github.com/NebulousLabs/Sia-GPU-Miner/releases/download/v1.0/sia-gpu-miner-mac64.xz) and the wallet works fine but when I try to extract the miner it says file type not supported. I downloaded the unarchiver and it was able to extract the files. Once I extracted the sia-gpu-miner-mac64.xz file I had: Sia-UI-v0.3.3-beta-darwin.tar.xz (it came with the wallet I guess), a "sia-gpu-miner-mac64" file that opens in textedit, and another sia-gpu-miner-mac64.xz file. Do I need the CLI? I downloaded Sia_CLI_0.3.3-release.beta_darwin_amd64.zip but when I try to run siad I get: ****-MacBook-Pro:~ ****$ /Users/****/Downloads/sia/Sia_CLI_0.3.3-release.beta_darwin_amd64/siad ; exit; listen tcp :9981: bind: address already in use logout [Process completed] Anyone have any ideas? I really want to be able to mine and sell storage but I can't seem to get it working. Thanks! Sounds like you have a zombie process of siad running. Try: killall -9 siad ./siad |
|
|
|
There's been a bit of confusion so I'll say it again:
Launch is on the 7th at noon EST. That's about 18.5 hours from the time this post was made.
A lot of people have been asking for features and tools like block explorers and mining pools. Please keep in mind that this coin is very young (fetus!), and doesn't have all the same infrastructure of some of the mature coins. But it will, we are actively working on building out the important parts of the coin. Thanks for being patient.
What? I thought this already launched. Is that why I have 13 blocks mined, but the wallet shows 0 SC? Coin's currently in testnet mode. In about 14 hours it'll launch fully. You should see your testnet coins count towards your balance once they confirm, which is 50 confirmations. On the actual network tomorrow, it'll take 144 confirmations. Any mining done between now and the actual launch won't mine actual Siacoins, only testnet coins which are often wiped on release anyway. |
|
|
|
|
Show Posts
