You can only write to Binance Chain via Transactions. Both Web API and Node RPC provide
a broadcastTx API to submit a signed and encoded transaction onto the Binance Chain. The detailed process is outlined below:

Encoding defines the way how transactions are serialized and transferred between clients and nodes,
and different nodes themselves. here is a detailed specification on the transaction
types and encoding logic.

Sign SHA256 of the encoded byte array, to create an ECDSA signature on curve Secp256k1 and serialize the R and S result into a 64-byte array. (both R and S are encoded into 32-byte big endian integers, and then R is put into the first 32 bytes and S are put into the last 32 bytes of the byte array. In order to break S 's malleability, S set to curve.Order() - S if S > curnve.Order()/2.)

The signature will be encoded together with transaction message and sent as payload to Binance Chain node via RPC or http REST API, as described in the above section.

After Account is created, besides the balances, Account also contains:

Account Number: an internal identifier for the account

Sequence Number: an ever-changing integer.

The Sequence Number is the way how Binance Chain prevents Replay Attack (the idea is borrowed from Cosmos
network, but varies a bit in handling). Every transaction should have a new Sequence Number increased by
1 from the current latest sequence number of the Account, and after this transaction is recorded on the
block chain, the Sequence Number will be set to the same number as the one of latest transaction.

This logic forces the client to be aware of the current Sequence Number, either by reading from the
blockchain via API, or keep the counting locally by themselves. The recommended way is to keep
counting locally and re-synchronize from the blockchain periodically.