Topic: [ANN][XCP] Counterparty - Pioneering Peer-to-Peer Finance - Official Thread - page 140. (Read 1276985 times)

Thanks. I will then wait until this is finished before I get my handy on some XCP but count me in once theres a working client

i think the BTC one is actually real, the rest is obviously a joke to get people thinking of what is possible, some day. hence "i can't believe this"

Here you go:

CoinDesk: http://www.coindesk.com/microsoft-adds-bitcoin-payments-xbox-games-mobile-content/
The Verge: http://www.theverge.com/2014/12/11/7375771/microsoft-supports-bitcoin-payments
PCWorld: http://www.pcworld.com/article/2858612/microsoft-starts-accepting-bitcoin-payments.html

(Hint, hint. It's a photoshop.)

Can we get another additional source for this please?

haha yes sorry i don't mean to ask for things after the fact that it was considered done, it was just that one detail.

i'll work on learning on running the contract today and hopefully someone else from the community can help me figure out how to test buying a ticket to a test lotto

thanks again

that is a strength not a weakness... trust me i saw first hand what having too much money too fast could do to a concept...

omg i can't believe this! 

https://twitter.com/chloregy/status/543053687342772224

In the meantime, you *can* run Counterwallet on your local computer---it's just not very user-friendly.

The desktop wallet is being developed. We'll keep you all posted on the progress

This is for all of us want.

Hello,

I am new to counterparty and just started getting into it.
First things first. Is there an actual client I can easily run on my own machine instead of using this web wallet thingy? I don't feel comfortable with this web based thingy.

 sufficient funds. XCP has a pretty good progress, but may be lack of funds for expanding and largely depends on the community support.

is there a connection between reddit and counterparty? - I think they want to go big on btc and probably want to integrate some advanced stuff.

How does the deadline for the lottery work?  Seems like it would be best to have a policy of setting a ticket purchase deadline of block X, Lottery takes place on Block X+10 (using block hash?), winners are paid on Block X+11.... or something like that.

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



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.

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

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.

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.


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.

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.

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.

 

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