[ANN][XCP] Counterparty - Pioneering Peer-to-Peer Finance - Official Thread

[prophetx]

Can you reply to this post with your XCP/BTC address.

Then I will send the link to the people who pledged to support your coding of this smart contract.

Here you go: 1LeygZteCpjBstARoyt3uHgPhV8aJHsBAg

Again, thank you so much for setting this up! I think this is the first cryptocurrency I've actually earned, rather than buying.

Also, as I didn't explicit a reward for the code review, if you would not mind perhaps sharing a % of it to the person who did the code review.  https://gist.github.com/jorisbontje/353f69515a16cef7de7b I will ask him to put his XCP/BTC address in the git repo.

I was definitely planning to pass some of the bounty to the code reviewer. As I said, it was a very good and thorough review. Does 20% seem fair to everyone?

Let me know if you have any other smart contract work you need done. And I'm still planning on trying out some code improvements over the next few days. I'll be happy to help debug if you run into any issues with your testing.

cool I put in the withdraw request of 50 xcp on poloniex to your address, i think they are installing a new server network card so it might take a few hours. I will post the tx ID when I see it.

I also sent an IM to all the others for the remaining amounts and will follow up.

just an update... poloniex is having withdraw issues with there system.... so it might take another 12-24 hours before their tech people figure out that they need to restart some processes...

tx finally went through

f06352ccd03301c9f40edbce625b6f97eb18ce49a0403be1b089e1983699c79c

http://blockscan.com/tx?txhash=f06352ccd03301c9f40edbce625b6f97eb18ce49a0403be1b089e1983699c79c

also i got one of the pledgees amounts incorrect, so the total you should receive is 110, not 115.  Sorry about was taking number from here and from skype chats and apparently got confused.

[semiel]

tx finally went through

f06352ccd03301c9f40edbce625b6f97eb18ce49a0403be1b089e1983699c79c

http://blockscan.com/tx?txhash=f06352ccd03301c9f40edbce625b6f97eb18ce49a0403be1b089e1983699c79c

also i got one of the pledgees amounts incorrect, so the total you should receive is 110, not 115.  Sorry about was taking number from here and from skype chats and apparently got confused.

I can confirm I got the 50 XCP, plus two separate 10 XCP transactions. Thanks, prophetx, ivana, and mysterious third person!

I'll bug Joris for his address and forward him 20% of whatever I end up receiving.

[Anotheranonlol]

... It would be good if there was a toggle switch on block explorer to hide/show numerical assets.

The toggle switch is next to the "Asset" column header (drop down box).  

I see it now, Thank you

[Matt Y]

tx finally went through

f06352ccd03301c9f40edbce625b6f97eb18ce49a0403be1b089e1983699c79c

http://blockscan.com/tx?txhash=f06352ccd03301c9f40edbce625b6f97eb18ce49a0403be1b089e1983699c79c

also i got one of the pledgees amounts incorrect, so the total you should receive is 110, not 115.  Sorry about was taking number from here and from skype chats and apparently got confused.

I can confirm I got the 50 XCP, plus two separate 10 XCP transactions. Thanks, prophetx, ivana, and mysterious third person!

I'll bug Joris for his address and forward him 20% of whatever I end up receiving.

I'm down for 20. Travelling now, will send tomorrow.

[weex]

What is the ELI5 on how to use the Multisig feature in Counterwallet?

I wanted to know the same, still new at this XCP features.

http://support.counterparty.io/support/solutions/articles/5000006561-multisig-tech-preview

Edit: Sorry, I didn't see that the question was for Counterwallet. I don't think it's in there yet.

[NexxusDrako]

http://edeniancredit.xcp.pw - http://kingdomofedenia.webs.com/ (a micro-nation - unfortunatly disolved)

You're kidding me? You found my old micronation?

Hahah, nice. I have a new one now though at http://vyktorydollar.xcp.pw which leads to http://vyktory.webs.com. We even have a MicroWiki page at http://mw.micronation.org/wiki/Commonwealth_of_Vyktory

Also, that Edenian Credit asset died as I was the victim of an XSS exploit that took my coins. The Edenius replaced it, then Edenia died. heh

[bitcoinrocks]

Did any news lead to the price downturn of late?

[pankogulo]

Quick update, All Counterparty Foundation Members will now receive SMS notification on important Counterparty updates, as well as a nice 'Members logo' to show off . The logo is in the making and will be sent out by the end of the week. http://counterpartyfoundation.org/new-membership-benefits-sms-notifications-and-members-logo/

[pankogulo]

Here's the weekly community update post: http://counterparty.io/news/counterparty-community-update-dec-10/

[Anotheranonlol]

Did any news lead to the price downturn of late?

No, you can see earlier one of the biggest whales cashing some funds to bter (largest address)
http://blockscan.com/address/1727McPbguq8FRMiUSzUs85eEG98sfzgvZ
maybe they decided to sell some. Although they must be dumb to try that, they really should be going down OTC route or at least really slow trickle sell with patience otherwise they are massively devauling their own stash

Perhaps more likely is someone offloading urgently- particularly if they are selling their entire holdings (in which case they don't care about what level they dump  to so much, in fact better for them if it stays low rather than bouncing up again)

e.g https://forums.counterparty.io/discussion/comment/4255/#Comment_4255

You can see clearly is single market orders dumping sequentially indicating a single trader,  not a bunch of them..but ofc one exchange tends to follow the other. Same story on polo which is even less liquid, And since market tend to trade on momentum of course others can join in on selling 'whilst it's going down'. in order to allow themselves to accumulate at a lower level.
 

{"date":1418059059,"price":0.01477,"amount":0.009,"tid":10373855,"type":"sell"},{"date":1418059059,"price":0.01477,"amount":0.008,"tid":10373856,"type":"sell"},{"date":1418059059,"price":0.01451,"amount":1.2,"tid":10373857,"type":"sell"},{"date":1418059059,"price":0.01451,"amount":4.924,"tid":10373858,"type":"sell"},{"date":1418059059,"price":0.01446,"amount":0.719,"tid":10373859,"type":"sell"},{"date":1418059059,"price":0.01441,"amount":13.879,"tid":10373860,"type":"sell"},{"date":1418059059,"price":0.01441,"amount":2.082,"tid":10373861,"type":"sell"},{"date":1418059059,"price":0.01419,"amount":1.057,"tid":10373862,"type":"sell"},{"date":1418059059,"price":0.01418,"amount":1.058,"tid":10373863,"type":"sell"},{"date":1418059059,"price":0.01417,"amount":9.015,"tid":10373864,"type":"sell"},{"date":1418059059,"price":0.01417,"amount":6.578,"tid":10373865,"type":"sell"},{"date":1418059059,"price":0.01415,"amount":2.12,"tid":10373866,"type":"sell"},{"date":1418059059,"price":0.01414,"amount":100.3,"tid":10373867,"type":"sell"},{"date":1418059059,"price":0.01408,"amount":36.949,"tid":10373868,"type":"sell"},{"date":1418059059,"price":0.01407,"amount":35.537,"tid":10373869,"type":"sell"},{"date":1418059059,"price":0.01406,"amount":189.26,"tid":10373870,"type":"sell"},{"date":1418059059,"price":0.01405,"amount":9.964,"tid":10373871,"type":"sell"},{"date":1418059059,"price":0.01404,"amount":9.964,"tid":10373872,"type":"sell"},{"date":1418059059,"price":0.01404,"amount":35.613,"tid":10373873,"type":"sell"},{"date":1418059059,"price":0.01403,"amount":0.114,"tid":10373874,"type":"sell"},{"date":1418059059,"price":0.01403,"amount":146,"tid":10373875,"type":"sell"},{"date":1418059059,"price":0.014,"amount":48.207,"tid":10373876,"type":"sell"},{"date":1418059059,"price":0.01394,"amount":100,"tid":10373877,"type":"sell"},{"date":1418059059,"price":0.01393,"amount":55.255,"tid":10373878,"type":"sell"},{"date":1418059059,"price":0.01393,"amount":0.02,"tid":10373879,"type":"sell"},{"date":1418059059,"price":0.01384,"amount":36.127,"tid":10373880,"type":"sell"},{"date":1418059059,"price":0.01382,"amount":10,"tid":10373881,"type":"sell"},{"date":1418059059,"price":0.01382,"amount":1,"tid":10373882,"type":"sell"}
-------------
{"date":1418102772,"price":0.01394,"amount":2.5,"tid":10378016,"type":"sell"},{"date":1418102772,"price":0.01393,"amount":2.154,"tid":10378017,"type":"sell"},{"date":1418102772,"price":0.01389,"amount":0.039,"tid":10378018,"type":"sell"},{"date":1418102772,"price":0.01385,"amount":2,"tid":10378019,"type":"sell"},{"date":1418102772,"price":0.01385,"amount":2.166,"tid":10378020,"type":"sell"},{"date":1418102772,"price":0.01384,"amount":3,"tid":10378021,"type":"sell"},{"date":1418102772,"price":0.01375,"amount":0.03,"tid":10378022,"type":"sell"},{"date":1418102772,"price":0.01374,"amount":6.703,"tid":10378023,"type":"sell"},{"date":1418102772,"price":0.01373,"amount":3.33,"tid":10378024,"type":"sell"},{"date":1418102772,"price":0.01373,"amount":4.897,"tid":10378025,"type":"sell"},{"date":1418102772,"price":0.0137,"amount":3,"tid":10378026,"type":"sell"},{"date":1418102772,"price":0.0137,"amount":2.544,"tid":10378027,"type":"sell"},{"date":1418102772,"price":0.01369,"amount":0.968,"tid":10378028,"type":"sell"},{"date":1418102772,"price":0.01366,"amount":10,"tid":10378029,"type":"sell"},{"date":1418102772,"price":0.0136,"amount":100,"tid":10378030,"type":"sell"},{"date":1418102772,"price":0.01359,"amount":50,"tid":10378031,"type":"sell"},{"date":1418102772,"price":0.01354,"amount":1.812,"tid":10378032,"type":"sell"},{"date":1418102772,"price":0.01351,"amount":39.008,"tid":10378033,"type":"sell"},{"date":1418102772,"price":0.0135,"amount":30,"tid":10378034,"type":"sell"},{"date":1418102772,"price":0.0135,"amount":35.849,"tid":10378035,"type":"sell"},
----
{"date":1418149386,"price":0.01386,"amount":0.017,"tid":10383907,"type":"sell"},{"date":1418149386,"price":0.01386,"amount":0.016,"tid":10383908,"type":"sell"},{"date":1418149386,"price":0.01386,"amount":0.016,"tid":10383909,"type":"sell"},{"date":1418149386,"price":0.01386,"amount":0.015,"tid":10383910,"type":"sell"},{"date":1418149386,"price":0.01385,"amount":53.357,"tid":10383911,"type":"sell"},{"date":1418149386,"price":0.0138,"amount":3.176,"tid":10383912,"type":"sell"},{"date":1418149386,"price":0.0138,"amount":0.144,"tid":10383913,"type":"sell"},{"date":1418149386,"price":0.01363,"amount":50.477,"tid":10383914,"type":"sell"},{"date":1418149386,"price":0.01363,"amount":2.47,"tid":10383915,"type":"sell"},{"date":1418149386,"price":0.0136,"amount":10,"tid":10383916,"type":"sell"},{"date":1418149386,"price":0.01356,"amount":36.88,"tid":10383917,"type":"sell"},{"date":1418149386,"price":0.01355,"amount":203.218,"tid":10383918,"type":"sell"},{"date":1418149386,"price":0.01354,"amount":36.928,"tid":10383919,"type":"sell"},{"date":1418149386,"price":0.01353,"amount":100,"tid":10383920,"type":"sell"},{"date":1418149386,"price":0.01352,"amount":36.982,"tid":10383921,"type":"sell"},{"date":1418149386,"price":0.01351,"amount":100,"tid":10383922,"type":"sell"},{"date":1418149386,"price":0.01351,"amount":0.296,"tid":10383923,"type":"sell"},{"date":1418149386,"price":0.01351,"amount":37.01,"tid":10383924,"type":"sell"},{"date":1418149386,"price":0.0135,"amount":186.373,"tid":10383925,"type":"sell"},{"date":1418149386,"price":0.0135,"amount":7.5,"tid":10383926,"type":"sell"},{"date":1418149386,"price":0.01332,"amount":14,"tid":10383927,"type":"sell"},{"date":1418149386,"price":0.0132,"amount":42.879,"tid":10383928,"type":"sell"},
{"date":1418149386,"price":0.01314,"amount":37.709,"tid":10383930,"type":"sell"},
----------------------------
{"date":1418175857,"price":0.01318,"amount":45.387,"tid":10385796,"type":"sell"},{"date":1418175857,"price":0.01318,"amount":7.587,"tid":10385797,"type":"sell"},{"date":1418175857,"price":0.01318,"amount":7.469,"tid":10385798,"type":"sell"},{"date":1418175857,"price":0.01318,"amount":0.386,"tid":10385799,"type":"sell"},{"date":1418175857,"price":0.01318,"amount":0.046,"tid":10385800,"type":"sell"},{"date":1418175857,"price":0.01318,"amount":0.047,"tid":10385801,"type":"sell"},{"date":1418175857,"price":0.01317,"amount":0.037,"tid":10385802,"type":"sell"},{"date":1418175857,"price":0.01316,"amount":2.11,"tid":10385803,"type":"sell"},{"date":1418175857,"price":0.01316,"amount":0.041,"tid":10385804,"type":"sell"},{"date":1418175857,"price":0.01315,"amount":0.114,"tid":10385805,"type":"sell"},{"date":1418175857,"price":0.01315,"amount":50,"tid":10385806,"type":"sell"},{"date":1418175857,"price":0.01315,"amount":14.88,"tid":10385807,"type":"sell"},{"date":1418175857,"price":0.01314,"amount":100.495,"tid":10385808,"type":"sell"},{"date":1418175857,"price":0.0131,"amount":4.334,"tid":10385809,"type":"sell"},{"date":1418175857,"price":0.01305,"amount":5,"tid":10385810,"type":"sell"},{"date":1418175857,"price":0.01303,"amount":19.8,"tid":10385811,"type":"sell"},{"date":1418175857,"price":0.01302,"amount":0.8,"tid":10385812,"type":"sell"},{"date":1418175857,"price":0.01302,"amount":50,"tid":10385813,"type":"sell"},{"date":1418175857,"price":0.01301,"amount":76.458,"tid":10385814,"type":"sell"},{"date":1418175857,"price":0.013,"amount":40,"tid":10385815,"type":"sell"},{"date":1418175857,"price":0.01292,"amount":37.244,"tid":10385816,"type":"sell"},{"date":1418175857,"price":0.01291,"amount":150,"tid":10385817,"type":"sell"},{"date":1418175857,"price":0.0129,"amount":100,"tid":10385818,"type":"sell"},{"date":1418175857,"price":0.01282,"amount":39.002,"tid":10385819,"type":"sell"},{"date":1418175857,"price":0.01281,"amount":80,"tid":10385820,"type":"sell"},{"date":1418175857,"price":0.01281,"amount":0.218,"tid":10385821,"type":"sell"},{"date":1418175857,"price":0.01281,"amount":39.032,"tid":10385822,"type":"sell"},{"date":1418175857,"price":0.0128,"amount":129.512,"tid":10385823,"type":"sell"},

 

[ianspain]

Thank you for the thorough review! I'll take a look at addressing the issues when I get the chance. (Might be a day or so.)

Update: I've made some quick fixes for the two issues identified as blockers. I've added test cases for both, and they're both pushed to the repo:

https://github.com/PeterBorah/ethereum-powerball

That might be enough to fulfill the conditions of the bounty. However, as a matter of professional pride, I want to spend a little more time working on the quality of the code. The sorts of bugs found reveal what the weak spots are, and I have some ideas for making it more robust.* So, I'm going to try to work on that over the next couple evenings.

* For the programmers in the audience: I've basically got an implicit state machine with some pretty complex effects. I want to model it more directly so that it's easier to reason about and harder to end up in weird partial states. I'm also not dealing with storing data in a very principled way, so I want to think about encapsulating some of that.

Can you reply to this post with your XCP/BTC address.

Then I will send the link to the people who pledged to support your coding of this smart contract.

Me - 50 XCP
Matt Y - 20 XCP
Ivana - 10 XCP
Niceplum - 10 XCP 5 XCP (edit sorry i made a mistake too many numbers )
Tyhmakulho - 10 XCP
Ian - 10 XCP
Dante - not sure, expressed interest
Tusk - 2 XCP
Jonathan O - 3 XCP

Grand total: 115 XCP 110 XCP (EDIT) or about $600 equivalent at today's rates.

I am going to ask them all to send it directly to you as I don't want to be the middleman. Anyone sending please post here to confirm (if you have a bitcointalk account, some people may not).

Also, as I didn't explicit a reward for the code review, if you would not mind perhaps sharing a % of it to the person who did the code review.  https://gist.github.com/jorisbontje/353f69515a16cef7de7b I will ask him to put his XCP/BTC address in the git repo.

I have not had time yet to get this running on the testnet to try it out but will spend some time this week to learn how to do that (haven't run counterpartyd since Feb so that will be interesting...), and then am also asking some people around who know people in the gaming space to see if we could perhaps demo this capability for them and get them interested in using XCP and Ethereum for their business.

Thanks!  

Hi guys, just sent my 10 xcp from Poloniex

[deliciousowl]

What is the ELI5 on how to use the Multisig feature in Counterwallet?

To send to a multisig address, just put in the destination field a multisig (m of n) address with this format: n_address1_address2_m

In order to set up your own multi-sig address, you do the following:

• Create 2 or 3 addresses in Counterwallet
• Make a regular transaction with each of these addresses, so that the pubkey of each address is visible on the blockchain.

Then you be able to add these as a multi-sig address here (following the same format 2_address1_address2_m or 3_address1_address2_address3_m):



Now you can use your multi-sig address like a normal address to make a (or any type of) transaction. However because it is a multi-sig transaction, you will get an unsigned raw transaction. In order to broadcast it, you will need to sign it with each address (varies based on your chosen m-of-n).

You can use the "sign transaction" action for each corresponding address that is required to make it valid.


Hope that helps!

[cntrdr]

Thank you for the thorough review! I'll take a look at addressing the issues when I get the chance. (Might be a day or so.)

Update: I've made some quick fixes for the two issues identified as blockers. I've added test cases for both, and they're both pushed to the repo:

https://github.com/PeterBorah/ethereum-powerball

That might be enough to fulfill the conditions of the bounty. However, as a matter of professional pride, I want to spend a little more time working on the quality of the code. The sorts of bugs found reveal what the weak spots are, and I have some ideas for making it more robust.* So, I'm going to try to work on that over the next couple evenings.

* For the programmers in the audience: I've basically got an implicit state machine with some pretty complex effects. I want to model it more directly so that it's easier to reason about and harder to end up in weird partial states. I'm also not dealing with storing data in a very principled way, so I want to think about encapsulating some of that.

Can you reply to this post with your XCP/BTC address.

Then I will send the link to the people who pledged to support your coding of this smart contract.

Me - 50 XCP
Matt Y - 20 XCP
Ivana - 10 XCP
Niceplum - 10 XCP 5 XCP (edit sorry i made a mistake too many numbers )
Tyhmakulho - 10 XCP
Ian - 10 XCP
Dante - not sure, expressed interest
Tusk - 2 XCP
Jonathan O - 3 XCP

Grand total: 115 XCP 110 XCP (EDIT) or about $600 equivalent at today's rates.

I am going to ask them all to send it directly to you as I don't want to be the middleman. Anyone sending please post here to confirm (if you have a bitcointalk account, some people may not).

Also, as I didn't explicit a reward for the code review, if you would not mind perhaps sharing a % of it to the person who did the code review.  https://gist.github.com/jorisbontje/353f69515a16cef7de7b I will ask him to put his XCP/BTC address in the git repo.

I have not had time yet to get this running on the testnet to try it out but will spend some time this week to learn how to do that (haven't run counterpartyd since Feb so that will be interesting...), and then am also asking some people around who know people in the gaming space to see if we could perhaps demo this capability for them and get them interested in using XCP and Ethereum for their business.

Thanks!  

Dante just sent 2 XCP.

[semiel]

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.

[prophetx]

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

[Equality 7-2521]

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 it’s intended for testing and development purposes only.  Also, please don’t flood the server with requests.

[semiel]

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%.

It should be fairly easy to modify the code to work that way. However, I strongly recommend against it. That would make the game completely undesirable to play.

Think about it this way: Your chance of getting a jackpot is 1 in 175,223,510. That's true no matter who else plays, or how much the prize is. Because of that, there's only one value that's a "fair" payout for a jackpot: 175,223,510 times the cost of a ticket, minus the house's cut.

You're never, ever going to sell 175,223,510 tickets for your lottery, at least not until you're as big as real Powerball. Because of that, you simply won't bring in enough money in tickets to make the jackpot attractive. Imagine the first person to buy a ticket: they'll have a 1:175,223,510 chance of hitting the jackpot, and their expected payout if they do will be half the cost of the ticket they just bought...

Luckily, your chances of having to pay out are equally low, so if you set the payouts correctly and buy insurance/have the money lent to you/whatever you can expect a profitable return on average over time.

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

Each contract can only run one lotto at a time, as currently set up. If you had a system with lots of lottos running simultaneously, you'd probably want to maintain a list of lotto contracts, maybe with some sort of way of automatically registering and displaying them. They'll have a static address, so you can always "find" it once you know where to look for it.

[prophetx]

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%.

It should be fairly easy to modify the code to work that way. However, I strongly recommend against it. That would make the game completely undesirable to play.

Think about it this way: Your chance of getting a jackpot is 1 in 175,223,510. That's true no matter who else plays, or how much the prize is. Because of that, there's only one value that's a "fair" payout for a jackpot: 175,223,510 times the cost of a ticket, minus the house's cut.

You're never, ever going to sell 175,223,510 tickets for your lottery, at least not until you're as big as real Powerball. Because of that, you simply won't bring in enough money in tickets to make the jackpot attractive. Imagine the first person to buy a ticket: they'll have a 1:175,223,510 chance of hitting the jackpot, and their expected payout if they do will be half the cost of the ticket they just bought...

Luckily, your chances of having to pay out are equally low, so if you set the payouts correctly and buy insurance/have the money lent to you/whatever you can expect a profitable return on average over time.

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

Each contract can only run one lotto at a time, as currently set up. If you had a system with lots of lottos running simultaneously, you'd probably want to maintain a list of lotto contracts, maybe with some sort of way of automatically registering and displaying them. They'll have a static address, so you can always "find" it once you know where to look for it.

ok, so i think you just need to put in an operator that says that if no one get 6 of 6 then, 5 of 6 inherits the pay out of 6 of 6, and if not 5 of 6 then 4 of 6 inherits the pay out of 5 of 6 and 6 of 6, and so forth.  this way the lotto stays attractive and does not require someone to have $1M to run.

would that be possible for you to add that? please

so the contract is attached to the btc address that runs the contract?  i'm just not understanding the mechanics of how this interfaces with the XCP/BTC system/network so that another address holder (not the initiator of the contract) can purchase a ticket.  so the initiator runs this against counterpartyd (I have to figure out how that works), and then a player would also run this (i think) against his instance of counterpartyd, but what i do not understand is how the player is able to identify the contract on the blockchain to send a message that he is purchasing a ticket against that particular instantiation of the contract.

I know you are not familiar with how XCP works and the ethereum port, so it may be that someone else needs to answer how that actually happens.

[Tyhmakulho]

I can confirm I got the 50 XCP, plus two separate 10 XCP transactions. Thanks, prophetx, ivana, and mysterious third person!

I sent that second 10 XCP I am happy to support good projects when I am not technical person.

[semiel]

ok, so i think you just need to put in an operator that says that if no one get 6 of 6 then, 5 of 6 inherits the pay out of 6 of 6, and if not 5 of 6 then 4 of 6 inherits the pay out of 5 of 6 and 6 of 6, and so forth.  this way the lotto stays attractive and does not require someone to have $1M to run.

would that be possible for you to add that? please

Yeah, I can add that. I'm not sure how the probabilities will work out, but it shouldn't be too much of a problem from a technical perspective. I was going to try to make it more modular anyway, so maybe I'll let people plug in their own payout system. (I should probably say that I reserve the right to stop working on this at some point, if it gets to be more work than I signed up for. But for now I'm happy to keeping improving the code, especially since working on my Ethereum scripting skills is something I'd be doing anyway.)

so the contract is attached to the btc address that runs the contract?  i'm just not understanding the mechanics of how this interfaces with the XCP/BTC system/network so that another address holder (not the initiator of the contract) can purchase a ticket.  so the initiator runs this against counterpartyd (I have to figure out how that works), and then a player would also run this (i think) against his instance of counterpartyd, but what i do not understand is how the player is able to identify the contract on the blockchain to send a message that he is purchasing a ticket against that particular instantiation of the contract.

I know you are not familiar with how XCP works and the ethereum port, so it may be that someone else needs to answer how that actually happens.

Since I don't know how the XCP version works, I can't help you with too many specifics. But think about how transactions work: someone initiates them, but eventually they spread throughout the network. You can point to a specific transaction based on its id, and anyone on the network can see what the transaction was based on their own copy of the blockchain. Contracts are kinda like that. They live "on the blockchain", and anyone can interact with them the same way anyone can send a transaction to any address.