Quote from: prophetx on December 11, 2014, 01:32:02 AM

Quote from: semiel on December 11, 2014, 12:36:10 AM

Received contributions of 10, 5, and 2 XCP. Thanks ianspain, dante, and (presumably) niceplum!

I got Joris to send me his XCP address and add it to the gist. I've just sent him 22.4 XCP, which is 20% of the expected 112 (including dante's contribution).

More importantly, I've pushed a fix to a bug we missed. Until the fix, you were able to create tickets with repeated numbers, which would have much better odds than normal tickets.

I'm a broken record on this, but thanks to everyone who participated! It's pretty thrilling to be able to make a little money by working with random strangers who want to push this technology forward.

thanks again!

tomorrow i will start setting up everything on an aws instance (or does anyone know of a free host i can use?)

i'll probably have some questions for you.

also there is one thing i noticed that probably was not clear from all of the write ups, but the award sizes should actually be a percentage of the total amount in tickets collected not set amounts like in the powerball. would it be difficult for you to adjust this? that is what I meant by picking a distribution method/algo. sorry i am not super good at reading code.

Code:

Send an appropriate amount of funds to support the prizes you are configuring. Because Powerball-style lotteries have set prizes, you cannot rely on ticket sales to cover payouts.

for example, getting all numbers correct gets 50% of total (split evenly if multiple tickets), 5 of 6 gets 30%, 4 of 6 gets 10%, 3 of 6 gets 7%, 2 of 6 gets 3%, 1 of 5 gets 0%.

also another question regarding the "buy ticket" command

if there are multiple lotto's running, how does a buyer know which contract to buy the lotto ticket from? or is all that handled at the XCP layer?

sorry for all the noobish sounding questions but i'm using this as an excerise to learn how this ethereum stuff works

https://counterparty.freshdesk.com/support/articles/5000003524-how-do-i-get-started-developing-on-counterparty-

Using our public system for dev/testing

As a service to the community, the Counterparty team maintains a public counterpartyd/counterblockd/Counterwallet server.

Hostname: devtest.counterparty.io
counterpartyd RPC user / password: rpc / 1234
counterpartyd API Port: 4000 (testnet port is 14000)
counterblockd API Port: 4100 (testnet port is 14100)
Counterwallet access
Main net: devtest.counterwallet.io
Test net: devtest-testnet.counterwallet.io

Please note that we cannot make any guarantees about the availability of this system, as its intended for testing and development purposes only. Also, please dont flood the server with requests.