Quote:
Originally Posted by PKS Ace
Somewhat in this vein of thought, to solve the problem of the site holding on to everyone's 'cash' at once, couldn't each user keep their bitcoins on their personal computers or in a bitcoin ewallet, and just have the software automatically send money to whoever is hosting the game you're sitting in whenever you buy in or top off at the table?
I'm about to get a bit technical so everyone else close your minds- it's not for you. I snipped a lot of your message, but I'm responding to that too.
When a new coin is created, it's done by a computer finding a solution to a mathematical problem (SHA hashes). Once it finds the solution, it broadcasts the coin which is signed with it's own key to the surrounding nodes who verify and check that the transaction is valid.
They then incorporate this new coin belonging to that node into their block chain. The block chain is never ending story of money flows in the economy. Everyone can see where and how the coins are spent. Any node that tries to generate false coins is caught out and shunned as a cheater because the hashes don't match. When you spend a coin, you're actually signing it with the key of the receiver. The surrounding nodes verify using public-key encryption that it's actually you that's signing the coin and incorporate it into their block-chain. Other nodes verify those block chains generated by the verifiers are correct and pass it on.
All this process takes time. When you spend a coin it might take a few seconds before a node picks it up and starts checking (0/Unconfirmed)... a couple of minutes before 1 or 2 nodes confirms it (1/Confirming) and maybe 15 mins before you can be reasonably sure that the payment is genuine (6/Confirmed). By now it's very unlikely there's any wrong-doing.
If you wanted to be able to spend quickly, you'd need to somehow verify that coin has been signed with your key. All security systems are based on networks of trust, and anyone who says otherwise is lying. One way I imagine could be possible would be using statistical methods to quickly generate a bayesian identity that the transaction is genuine to a large degree (60%) combined with a tit-for-tat approach if the node turns out to be a scammer by blackening his name.
For more details on the bayesian concept, see my article,
https://n-1.cc/pg/blog/openid_44398/...esian-security
Quote:
One possible solution I see to solving the problem of bots and autocalculators/etc while still allowing custom clients would be sending images instead of text hole cards. Have users submit images that are different enough that an OCR method would have trouble keeping up, but that wouldn't significantly impede people reading their cards or the action. Then when the Ac needed to be sent, a random image of Ac would then be pulled from a bank of hundreds of Ac's, and the user would receive this image when they were dealt that card.
More thoughts like this. The correct creative direction to be heading. Issues I see are:
- Custom theming for tables.
- Bandwidth usage increases loads (right now the protocol is very minimal and low-bandwidth) so it'd increase costs a ton. Would it be worth the trade-off?