However some top of the book update can result in an entire level disappearing. In that case, both price and volume changed actually at the same time, yet according to this example it will be broken down into two messages? This will lead to inconsistent state of the book when I read it between two messages. Or did the example just happen to show one field per message, and multiple fields per message are possible too?
Back in the day `aws ec2 get-console-output --instance-id $ID` used to contain the public key that can be extracted using regex. Not sure if this still works.
Notably, you don't need to post $N to make this bet. PredictIt calculates your worst case scenario and holds only that money. A set of "No" shares worth N-1.12, if it existed, would be literally free to hold. Fees are included in that calculation, but also fees are based on the difference between that cost to hold and the return. So yes, profits mean different things in different parts of that calculation in this degenerate case.
A full set of Nos worth N-1 would be a guaranteed loss of $0.10 per share from fees. PredictIt would hold that 10¢ and you would never see it again.
It's suppose to be clarifying between
a=1
b=2
and
a = [1,2]
b = [1,2]
For example "Give the cookies and brownies to Angie and Bob" could mean both Angie and Bob get both cookies and brownies. "Give the cookies and brownies to Angie and Bob, respectively" clarifies that the cookies go to Angie, and the brownies go to Bob.