Blocked
Blocked

0 Members and 1 Guest are viewing this topic.

gizmotron

  • Guest
I'm working on creating a simple to use XML scheme for Roulette. The purpose is to allow differing programmers and system simulations a common functioning interface of data exchange. An example would be common data for placement of bets and the amounts of these bets. Another example would be for recording results spin by spin in a common reference.

There has been talk about a live game testing environment for multi-users. There is a need to transmit the same spins to all involved. I'm suggesting an encrypted array of spins can be transmitted to end users that can make there bet selections and then send back the full results, showing each bet & results per spin, or just showing the total results in order to mask the method. In this way different programmers can create their own gambling environments if they want to try different experiments with the same spins.

Several encryption schemes can be shared among active programmers for data sharing. I have my own Blowfish(CBC) version that is bomb proof. I might be able to run it as a CGI on a server too.

I want an on-line testing application that allows anyone to try their methods against other players that want to with their own methods. What is needed is data sharing that can't be manipulated. The same goes for sharing spins too. I also want to create an RNG that is conceptually more random than the concepts used by Random.org. This RNG scheme should be published too. It could be based on real world physics and American & European wheels.

I already have a basic construct & spin telemetry that needs work.

 <rouletteRide version="1.2">
<spin>
  <spinNumber>1</spinNumber>
  <thisSpin>25</thisSpin>
  <realSpin>true</realSpin>
  <betEnt>1</betEnt>
  <theBetField>1,2,3,4,5,6,7,8,9,10,11,12,</theBetField>
  <bot18></bot18>
  <top18></top18>
  <odd></odd>
  <even></even>
  <red></red>
  <black></black>
  <1st12></1st12>
  <2nd12></2nd12>
  <thrd12></thrd12>
  <lowr></lowr>
  <midr></midr>
  <topr></topr>
</spin>
<spin>
  <spinNumber>2</spinNumber>
  <thisSpin>30</thisSpin>
  <realSpin>true</realSpin>
  <betEnt>1</betEnt>
  <theBetField>1,2,3,4,5,6,7,8,9,10,11,12,</theBetField>
  <bot18></bot18>
  <top18></top18>
  <odd></odd>
  <even></even>
  <red></red>
  <black></black>
  <1st12></1st12>
  <2nd12></2nd12>
  <thrd12></thrd12>
  <lowr></lowr>
  <midr></midr>
  <topr></topr>
</spin>
<spin>
  <spinNumber>3</spinNumber>
  <thisSpin>1</thisSpin>
  <realSpin>true</realSpin>
  <betEnt>1</betEnt>
  <theBetField>1,2,3,4,5,6,7,8,9,10,11,12,</theBetField>
  <bot18></bot18>
  <top18></top18>
  <odd></odd>
  <even></even>
  <red></red>
  <black></black>
  <1st12></1st12>
  <2nd12></2nd12>
  <thrd12></thrd12>
  <lowr></lowr>
  <midr></midr>
  <topr></topr>
</spin>
<spin>
  <spinNumber>4</spinNumber>
  <thisSpin>21</thisSpin>
  <realSpin>true</realSpin>
  <betEnt>1</betEnt>
  <theBetField>1,2,3,4,5,6,7,8,9,10,11,12,</theBetField>
  <bot18></bot18>
  <top18></top18>
  <odd></odd>
  <even></even>
  <red></red>
  <black></black>
  <1st12></1st12>
  <2nd12></2nd12>
  <thrd12></thrd12>
  <lowr></lowr>
  <midr></midr>
  <topr></topr>
</spin>
<spin>
  <spinNumber>5</spinNumber>
  <thisSpin>2</thisSpin>
  <realSpin>true</realSpin>
  <betEnt>1</betEnt>
  <theBetField>1,2,3,4,5,6,7,8,9,10,11,12,</theBetField>
  <bot18></bot18>
  <top18></top18>
  <odd></odd>
  <even></even>
  <red></red>
  <black></black>
  <1st12></1st12>
  <2nd12></2nd12>
  <thrd12></thrd12>
  <lowr></lowr>
  <midr></midr>
  <topr></topr>
</spin>
<spin>
  <spinNumber>6</spinNumber>
  <thisSpin>23</thisSpin>
  <realSpin>true</realSpin>
  <betEnt>1</betEnt>
  <theBetField>1&2&3@1,4&5&6@1,</theBetField>
  <bot18></bot18>
  <top18></top18>
  <odd></odd>
  <even></even>
  <red></red>
  <black></black>
  <1st12></1st12>
  <2nd12></2nd12>
  <thrd12></thrd12>
  <lowr></lowr>
  <midr></midr>
  <topr></topr>
</spin>
<spin>
  <spinNumber>7</spinNumber>
  <thisSpin>17</thisSpin>
  <realSpin>true</realSpin>
  <betEnt>1</betEnt>
  <theBetField>1&2&3@1,4&5&6@1,</theBetField>
  <bot18></bot18>
  <top18></top18>
  <odd></odd>
  <even></even>
  <red></red>
  <black></black>
  <1st12></1st12>
  <2nd12></2nd12>
  <thrd12></thrd12>
  <lowr></lowr>
  <midr></midr>
  <topr></topr>
</spin>
<spin>
  <spinNumber>8</spinNumber>
  <thisSpin>11</thisSpin>
  <realSpin>true</realSpin>
  <betEnt>1</betEnt>
  <theBetField>1&2&3@1,4&5&6@1,</theBetField>
  <bot18></bot18>
  <top18></top18>
  <odd></odd>
  <even></even>
  <red></red>
  <black></black>
  <1st12></1st12>
  <2nd12></2nd12>
  <thrd12></thrd12>
  <lowr></lowr>
  <midr></midr>
  <topr></topr>
</spin>
<spin>
  <spinNumber>9</spinNumber>
  <thisSpin>12</thisSpin>
  <realSpin>true</realSpin>
  <betEnt>1</betEnt>
  <theBetField>1&2&3@1,4&5&6@1,</theBetField>
  <bot18></bot18>
  <top18></top18>
  <odd></odd>
  <even></even>
  <red></red>
  <black></black>
  <1st12></1st12>
  <2nd12></2nd12>
  <thrd12></thrd12>
  <lowr></lowr>
  <midr></midr>
  <topr></topr>
</spin>
<spin>
  <spinNumber>10</spinNumber>
  <thisSpin>2</thisSpin>
  <realSpin>true</realSpin>
  <betEnt>1</betEnt>
  <theBetField>1&2&3@1,4&5&6@1,</theBetField>
  <bot18></bot18>
  <top18></top18>
  <odd></odd>
  <even></even>
  <red></red>
  <black></black>
  <1st12></1st12>
  <2nd12></2nd12>
  <thrd12></thrd12>
  <lowr></lowr>
  <midr></midr>
  <topr></topr>
</spin>
<s1>1,2,3,4,5,6,7,8,9,10,11,12,</s1>
<s2>1&2&3&4&5&6@6,7&8&9&10&11&12@6,</s2>
<s3>1&2&3@1,4&5&6@1,</s3>
<s4>0&00&1&2&3@5,</s4>
<s5>0&00&1&2&3&4@6,</s5>
<s6>1,2,3,4,20,21,22,23,24,25,</s6>
<s7>1,2,3,0,00,27,28,5,6,17,18,31,32,</s7>
<s8>7,8,15,16,11,12,23,24,29,30,</s8>
</rouletteRide>


My current program takes this telemetry and reassembles the game with each bet result. My point is that you can share every betting move, spin by spin this way. Telemetry like this can be encrypted so that it can't be manipulated. We could publish encrypted spins to all, and then each player could make available encrypted results that they can't manipulate either. After each game the result's encryption key can be made available. Yes, that does imply a two key method, one for spins, and one for results.

Now all this could be done live on the internet too. I just wanted the results of live play to have a telemetry language. A universal telemetry language can be more useful than just a bunch of independent programmers working with single language data transfers.

Any thoughts or suggestion are welcome.

gizmotron

  • Guest
OK, let's bring it down to every man's perspective.

If you had a test tool, now, that could run competitions, could you use the simple text entry format for placing your bets?

Examples:

"dozen1to12@20" -- this is placing 20 chips on the first dozen

"column3to36@20" -- this is placing 20 chips on the third column

"odd@50" -- this is placing 50 chips on odd

"red@6" -- this is placing six chips on red

"1-2-3-4-5-6@6" -- this is placing six chips on the double street 1-6

"1-2-3-4-5-6@1" -- this is placing one chip on the double street 1-6

"1,2,3,4,5,6," -- this is placing the default value on each of these six locations

"11,12,30,34,35,16," -- this is placing the default value on each of these six locations

"1-2-3-4-5-6@6,7-8-9-10-11-12@6" -- this is the same as betting 12 on the first section dozen

"1-2-3-4-5-6-7-8-9-10-11-12@12" -- this is the same as betting 12 on the first section dozen

The "-" separates each number in a list of numbers when including "@"

The "@" tells the value bet for all numbers in that list

The "," separates all bets

------------

Yes, No, any questions?


gizmotron

  • Guest
So how does the Competition Black Box work?

It has an encrypted set of spins, provided by automatic generation of the killer RNG, that will be posted to the internet before a challenge. The secret encryption key will appear to the provider after 5 - 10 - 15 minutes? The creator of the spins will have the option to set the spin rate, example 30 seconds, one minute, or two minutes apart. The creator won't even know the spins. The creator will send the encryption key to those playing the game by posting it. The players will enter that encryption key and the game will start. A player can quit any time. The encrypted list of spins will run each spin on the set intervals sent with the list. When a player quits his session, that session's results will be encrypted and placed on the clipboard & saved as a text file that is compressed and base(64) encoded.

You can then post your results as that encrypted, compressed, and encoded data on the competition's thread. A volunteer can decode each entry and post the results. You can use the Competition Black Box to view everyone's results on your own. After the competition deadline has passed the decode key can be published. There will be no way to cheat. You will not have access to your own telemetry while the competition timer is running. Anyone will be able to create spin lists, encryption keys, and act as volunteers. You will be able to view your as-you-play results. You will not be able to change them because a hidden recorder is where a duplicate will exist that is the source for your game.

Does that interest anyone?

bliss

  • Guest
Sounds good Gizmo. Are you planning on doing all the coding for this?

I thought Victor had something similar in mind. Perhaps he could elaborate on it in this thread.

gizmotron

  • Guest
Sounds good Gizmo. Are you planning on doing all the coding for this?

I thought Victor had something similar in mind. Perhaps he could elaborate on it in this thread.

That's why the suggestion for a basic construct. Additional features can be added to the main set of defined formations later. But for now a basic transfer language would be a first start or first step. I have at least 70% of this built already. It would take a while to build the first Black Box concept, that people could be download for free.