correct magic bytes values in readme

[nicolasochem]

No description provided.

[harryttd]

0x03 could also be votes now and not just transfers. The signer checks for that:

tezos-kms-signer/src/sigreq.py

Lines 36 to 53 in 926601f

	elif self.data[0] == 0x03: # Operation, for now, we only do ballots
	self.chainid = None
	self.type = "Unknown operation"
	self.blockhash = self.data[1:32] # The block hash
	if self.data[33] == 0x06: # 0x06 is a ballot
	self.pkh_type = self.data[34] # Public Key Hash type
	self.pkh = self.data[35:55] # Public Key Hash
	self.period = self.data[55:59]
	self.proposal = self.data[59:91]
	if self.data[91] == 0x00:
	self.type = "Ballot"
	self.vote = "yay"
	elif self.data[91] == 0x01:
	self.type = "Ballot"
	self.vote = "nay"
	elif self.data[91] == 0x02:
	self.type = "Ballot"
	self.vote = "pass"

Also maybe add

Suggested change

	* Does the message begin with a 0x11, 0x12 or 0x13? Indicating it is a baking or endorsement, rather than a 0x03 transfer.
	* Does the message begin with a 0x11, 0x12 or 0x13? Indicating it is a baking, preendorsement, or endorsement, rather than a 0x03 transfer.

[nicolasochem]

actually we should forbid any 0x03 operation. With a consensus key baker, you vote with the baker key, not the consensus key.

[harryttd]

That's assuming all users would use a consensus key. But i don't think we need to restrict them to that. As far as i can tell, there is no issue with allowing votes. If we keep the voting we should add in that voting ops are accepted.