A computer-implemented transfer method comprising the steps of: generating a Pay-to-script-hash (P2SH) blockchain transaction (Tx) having an output (TxO) related to: a digital asset which is a quantity of cryptocurrency (B 1) for transfer from a first party (I) to a second party (A); and a locking script comprising a hash (H1) of a redeem script (RS1) which takes the form of: the number of valid signatures required to satisfy the redeem script to unlock the transaction; at least one metadata (MD1) comprising a token (T1) which is a representation of, or a reference to, a tokenised entity, wherein the metadata: i) takes the place of a public key in the redeem script at a location which is designated in a blockchain protocol as a location for a cryptographic key such that it is interpreted by a blockchain protocol as a cryptographic key; and ii) includes parameters relating to the token (T1); at least one public cryptographic key which corresponds to a signature that can unlock the transaction and forms a cryptographic pair with a corresponding private key; and the total number of positions in the redeem script taken by the at least one metadata and the at least one public cryptographic key. generating a Pay-to-script-hash (P2SH) blockchain transaction (Tx) having an output (TxO) related to: a digital asset which is a quantity of cryptocurrency (B 1) for transfer from a first party (I) to a second party (A); and a locking script comprising a hash (H1) of a redeem script (RS1) which takes the form of: the number of valid signatures required to satisfy the redeem script to unlock the transaction; at least one metadata (MD1) comprising a token (T1) which is a representation of, or a reference to, a tokenised entity, wherein the metadata: i) takes the place of a public key in the redeem script at a location which is designated in a blockchain protocol as a location for a cryptographic key such that it is interpreted by a blockchain protocol as a cryptographic key; and ii) includes parameters relating to the token (T1); at least one public cryptographic key which corresponds to a signature that can unlock the transaction and forms a cryptographic pair with a corresponding private key; and the total number of positions in the redeem script taken by the at least one metadata and the at least one public cryptographic key. the number of valid signatures required to satisfy the redeem script to unlock the transaction; at least one metadata (MD1) comprising a token (T1) which is a representation of, or a reference to, a tokenised entity, wherein the metadata: i) takes the place of a public key in the redeem script at a location which is designated in a blockchain protocol as a location for a cryptographic key such that it is interpreted by a blockchain protocol as a cryptographic key; and ii) includes parameters relating to the token (T1); i) takes the place of a public key in the redeem script at a location which is designated in a blockchain protocol as a location for a cryptographic key such that it is interpreted by a blockchain protocol as a cryptographic key; and ii) includes parameters relating to the token (T1); at least one public cryptographic key which corresponds to a signature that can unlock the transaction and forms a cryptographic pair with a corresponding private key; and the total number of positions in the redeem script taken by the at least one metadata and the at least one public cryptographic key. <EOS>