I’ll post in this thread when I have fresh AMI’s out in a bit…I just finished the build of debs of the 1.0.0 release on Ubuntu on a Xeon processor, and will be updating things right now
How many sol/s do you get?
I’m getting a bit less than 1 Sol/s per core on c3 instances right now with the zcash teams build, I’ll see what I get on the Xeon built one in a bit (its been higher up until now).
What is your Sol/S? My AWS instance (m4.2xlarge) is only pulling 0.1Sol/s…
addnode=mainnet.z.cash
rpcuser=username
rpcpassword=useastrongone
genproclimit=numberofcores
gen=1
equihashsolver=tromp
Then run ~/zcash/./src/zcashd to see your hashrate
A c3.xlarge is getting 2.8 sol/sec right now on my new build, but it just started and that’s still rising, a c3.2xlarge is getting 5.5 sol/sec…but again, they JUST started up less than 10 minutes agin and that rises.
you can don’t need all the “./src” stuff to run things when you install from the deb’s
1 Like
A new image that has sprout pre-installed is out in the Northern California (us-west-1) region with AMI ID of ami-28d79c48
I’m pushing fresh images to all other regions as I type
Sao Paolo is released with AMI ami-b8821ed4
New images available in all regions running sprout!
When you launch, search for Sprout in “Community AMIs”…full list of IDs in a moment
AMI IDs for fresh images running sprout:
us-east-1 ami-861a4291
us-east-2 ami-6e58020b
us-west-1 ami-28d79c48
us-west-2 ami-56fc5a36
ap-south-1 ami-3d4b3f52
ap-northeast-2 ami-fd37e393
ap-southeast-1 ami-3d4eef5e
ap-southeast-2 ami-4a7b4729
ap-northeast-1 ami-2c02a14d
eu-central-1 ami-e9699186
eu-west-1 ami-52753e21
sa-east-1 ami-b8821ed4
Up and running in minutes - nice job, David.
A few questions from a guy who has been looking a zcash for over a month, but is still a little new to this;
I’d previously setup an AWS miner using Austin-Williams guide. What’s the difference between your turn-key and the solution that one has using his guide?
I wanted to install htop but by default your turn-key doesn’t have the right packages. Not a big deal, but wondered if that was a conscious choice?
My ami, you just boot it up and its mining
With mine you also don’t have to worry about all the keyspace issues he talks about, as he has that issue because he’s run zcashd before he clones the image, whereas mine has no wallet.dat or blockchain on it, each one you spin up generates a fresh wallet and syncs the blockchain on its own
1 Like
I was in a rush to get new images out today with Sprout on them, or I’d have included my script to auto-sweep coins into a zaddr
hereas mine has no wallet.dat or blockchain on it, each one you spin up generates a fresh wallet and syncs the blockchain on its own
Okay - but say I boot multiple instances of your turn-key, then I have to keep track of three separate copies of the wallet.dat file? Or am I mis-understanding that point?
I’d have included my script to auto-sweep coins into a zaddr
I’d be interested in seeing that.
yes, if you mine any coins you need to backup the wallet.dat files or move the coins to an address in a central wallet. The testnet should be calmed down enough soon (hopefully!) for me to mine some TAZ, as I don’t want to toss in features that move coins around into my AMI’s unless I have tested them first.
Hello Radix,
are the AMI IDs public?
Kind REgards,
Larissa
as I don’t want to toss in features that move coins around into my AMI’s unless I have tested them first.
Excellent - I’ll keep an eye on this space.
Yes, in ALL regions!! The lazy among us can just do a search for “zcash” or “sprout” in Community AMIs rather than cutting or pasting them 
I took me a lot of hours to make images… You Post could save me a lot of time
But I didnt do this:
ssh ubuntu@Your_instance_IP
wget https://apt.z.cash/pool/main/z/zcash/zcash-1.0.0-sprout-amd64.deb
Is it nessecery for better performance?