Topic: [ANN][CHIPS] KMD platform's LN app with realtime betting+decentralized shuffling - page 21. (Read 44571 times)

GAME.40898
broadcast.({"method":"start0","numplayers":10,"numrounds":3,"range":36})
136 81 232 147 86 204 12 215 31 182 calc_sharenrs deckid.e3cba5821df40e40baabd444297ef7679216f31abe31fcd890f6b49a3d75601f
0 1 2 3 4 5 6 7 8 9 size 11520 numplayers.10 range.36, alloc.11578
createdeck {"agent":"bet","method":"createdeck","range":36,"pubkeys":["ff2f8ea2846a92e84d9afe6de34c40571ba78575cb27f57539e7ee586d264223", "9877679dac09c4330aa9e9d4b85ef4b4860dc0176ae6da02e254684f985e980c", "bc39aae4d133746fc7fdbe7b08c1595f537d29c49a5edec065fff86ee12ea35a", "89b773d19a41ac295dcbd5f5e9ab233e1b1c9525f84937353dd056fa76c9dc52", "5c0cebfba0beeec74e31406c53509c735d80c88b2da649857f13d7121983574a", "de13814f71810dccb62d5e16bcb2451828c52aafd62aa59f1b69de6ab2ec0215", "cab87008836562ce6e84a3c1c0c358978f4e34f12c56b80b8ab9bf662390c70c", "0f0770c5a07d3c418081a15c9fe3f2ff0e8159a7d8917599f04077e8b6d8ee53", "0980a272621faa5a513fa3fbd9350b114d6934f6fa9aae9de8409d84df32be2f", "cc105e92ba9f9b9585adcb550f9a6d1aacf395e41022661f4d4a4b816a3e571f"]} -> (234884) max.234884
BET_roundstart numcards.36 numplayers.10
0 1 2 3 4 5 6 7 8 9 finished BET_roundstart numcards.36 numplayers.10
Gamestart.1503660744 vs 1503660746 Numplayers.10 Range.36 numplayers.10 numrounds.3
round.0 senderid.0 ([16])
BET_turni_next (0, 0) numplayers.10 range.36
round.0 senderid.1 ([1])
BET_turni_next (1, 0) numplayers.10 range.36
round.0 senderid.2 ([24])
BET_turni_next (2, 0) numplayers.10 range.36
round.0 senderid.3 ([33])
BET_turni_next (3, 0) numplayers.10 range.36
round.0 senderid.4 ([7])
BET_turni_next (4, 0) numplayers.10 range.36
round.0 senderid.5 ([18])
BET_turni_next (5, 0) numplayers.10 range.36
round.0 senderid.6 ([6])
BET_turni_next (6, 0) numplayers.10 range.36
round.0 senderid.7 ([6])
BET_turni_next (7, 0) numplayers.10 range.36
round.0 senderid.8 ([27])
BET_turni_next (8, 0) numplayers.10 range.36
round.0 senderid.9 ([29])
BET_turni_next (9, 0) numplayers.10 range.36
Round.0 completed
BET_statemachine_endround -> 0
round.1 senderid.0 ([13])
BET_turni_next (0, 1) numplayers.10 range.36
round.1 senderid.1 ([29])
BET_turni_next (1, 1) numplayers.10 range.36
round.1 senderid.2 ([13])
BET_turni_next (2, 1) numplayers.10 range.36
round.1 senderid.3 ([30])
BET_turni_next (3, 1) numplayers.10 range.36
round.1 senderid.4 ([24])
BET_turni_next (4, 1) numplayers.10 range.36
round.1 senderid.5 ([4])
BET_turni_next (5, 1) numplayers.10 range.36
round.1 senderid.6 ([20])
BET_turni_next (6, 1) numplayers.10 range.36
round.1 senderid.7 ([13])
BET_turni_next (7, 1) numplayers.10 range.36
round.1 senderid.8 ([8])
BET_turni_next (8, 1) numplayers.10 range.36
round.1 senderid.9 ([3])
BET_turni_next (9, 1) numplayers.10 range.36
Round.1 completed
BET_statemachine_endround -> 1
round.2 senderid.0 ([20])
BET_turni_next (0, 2) numplayers.10 range.36
round.2 senderid.1 ([4])
BET_turni_next (1, 2) numplayers.10 range.36
round.2 senderid.2 ([30])
BET_turni_next (2, 2) numplayers.10 range.36
round.2 senderid.3 ([27])
BET_turni_next (3, 2) numplayers.10 range.36
round.2 senderid.4 ([10])
BET_turni_next (4, 2) numplayers.10 range.36
round.2 senderid.5 ([15])
BET_turni_next (5, 2) numplayers.10 range.36
round.2 senderid.6 ([2])
BET_turni_next (6, 2) numplayers.10 range.36
round.2 senderid.7 ([6])
BET_turni_next (7, 2) numplayers.10 range.36
round.2 senderid.8 ([16])
BET_turni_next (8, 2) numplayers.10 range.36
round.2 senderid.9 ([4])
BET_turni_next (9, 2) numplayers.10 range.36
Round.2 completed
BET_statemachine_endround -> 2
Game completed next start.1503660746 vs 1503660746
------------------

The key is GAME.40898
which is one game every two seconds for a full day's stress test. I think for the basic gameplay loop it is working ok, but the problem is that it is kind of a hardcoded sequence and not very real world. While I wait for an updated lightning with reconnect issues fixed, I will generalize the game play side to handle more real world state machines

I have seen 10 tx/sec node to node LN sendpay, so once that side stabilizes, it will be fast enough for normal play. Slowly but surely things are progressing.

good thing you got that nice domain name!
feel free to make some template based website

So, what are project needs so far?

- Logo and branding design??
- Website
- Block Explorer

I think if we are going to have CHIPS listed on exchanges and make it listed on CoinMarketCap at least these 3 things are main needs to give as info to exchanges.

Now that CHIPS is becoming more and more real, it is time to recruit some mining pools and exchanges.

I am too busy for such things, but if you are able to, then please proactively push CHIPS forward. With the 10 second block rate, it is being mined at over 400,000 CHIPS/day

To get a listing, we need a graphical OP and a block explorer. If there are people here that can help with that, then I can pay for an exchange listing.

blocktimes are now very close to 10 seconds

considering CHIPS has had no marketing, nor much of any discussion, it is quite interesting that the hashrate has doubled in recent days

"blocks": 69872,
  "timeoffset": -4,
  "connections": 30,
  "difficulty": 0.01348656036015197,
 

that is double from the floor value, which we were only about halfway toward meeting, so it is more like a 4x increase in hashrate.

I continue to find bugs and issues with the c-lightning https://github.com/ElementsProject/lightning/issues

however, the issues I am seeing are expected for being the first one to really push it to its limits. So far I am quite pleased with how quickly the lightning devs actually respond and fix the bugs I am reporting.

Dealing with the lightning channels is quite a bit different than the normal API expected for payments, however it has quite a lot of similar aspects to barterDEX. The version 1 of Lightning wont support MofN approvals for payouts, which means that table stakes needs to be controlled by a dealer.

There are two ways around this, the first is to have the dealers deposit a performance bond and in the event of non-compliance to have a claim process using the signed game state transitions as proof of who should win the bet. The second is to have the blockchain process the signed data and allow spending of the performance bond if it is a valid claim.

Needless to say, the former is much easier to do and is a necessary first step for getting the full blockchain enforcement done.

Practically speaking, this means that if you go allin with more chips than the dealer's performance bond, you would be at risk, but for a first out release, this seems acceptable.

On the gameplay side, I got a 10 player roundrobin playing a meaningless game with no gameplay, but using encrypted deck, MofN card dealing, at about 1 second per game. Certainly an actual game state machine is needed, but I dont see many issues in that area once I get the gaming platform supporting betting, cashier and arbitrary gameplay strings.

Clearly, any blockchain enforcing of game claims will require a hardfork, but I am leaning toward doing that after the initial official release, so it will be a planned hardfork. It is getting more and more likely  that the current CHIPS chain will be the mainnet.

Is a pool in the making for this coin? Would like to participate then, too.

It's all about the merchandising.






Vintage jl777 action figure

It seems CHIPS is one of the few coins with a movie of the same name: http://www.imdb.com/title/tt0493405/

no pool yet, but solo mining is possible

Is there any pool available or is only solo mining possible?

Yeah i should have said "Finally first step for pangea" and yes i am excited. because CHIPS is exciting.
Anyway i managed to run a node with chipsd and LN daemon (149.202.49.218) with ubuntu 16.04 without any problem.
I also have 5 nodes on debian but only managed to build chipsd and chips-cli (and mining ). But i have problems to build the LN part, still trying. If someone could figure it out how to build it on debian 8 it could be cool.

mining is SHA256
currently it does not have much hashrate at all

the mining is cpu?

updated to new version with much larger OP_RETURN space
until an OP_RETURN that is bigger than 80 bytes is issued the network wont fork, as soon as there is, it will.

I dont expect to be testing the larger OP_RETURN until next week

Any guide to mining this anywhere? been watching these threads and it seems like an awesome idea and that you guys know what youre doing. Would love to be a part of it helping you create it but im technologically challenged.

blockrate is now 22 seconds per block with 16 peers over last day
  "blocks": 7119,

but it is 12 seconds/block in the recent hour

the chipsln project has a privatebet dir. from there run ./m_bet
then either ./host or ./client after there is a host running

for now it connects to localhost and just generates endless random setting games

however, it also publishes port 7797 where you can POST JSON requests with "agent":"chipsln" added to the various RPC that LN has intrinsically:

https://github.com/ElementsProject/lightning/blob/master/doc/lightning-invoice.7.txt
etc.

I have only tested getinfo, not sure about the RPC with params yet

It was quite painful, but I finally got the privatebet code to be able to issue a LN RPC call. it uses unix pipes and I had to link it into a subset of the LN codebase

at least they are now coexisting and I can expose a normal port base RPC

This can get more attention with couple of pools set up.