`csv
5Chi986mMWi8ksR2AEcz9VwuHw7DQdU6afB1GtqzkGo2iQN9,1000000000000
5FCTrcwzkr1uxxLAaTqfkB66NHBEDx2YoDGs3tcX8PM911hC,2000000000000
`

NOTE: On Kusama the values have 12 decimal places so the amounts in the example above are sending 1 and 2 KSM respectively.

$3

`sh
Usage: transfer [options]

Options:
--csv A CSV file formatted , on each line.
--cryptoType One of ed25519 or sr25519, depending on the crypto used to derive your keys. (default: "sr25519")
--wsEndpoint The endpoint of the WebSockets to connect. (default: "wss://cc3-4.kusama.network")
--suri The secret URI for the signer key.
-h, --help output usage information
`

$3

If you are sending transfers on Kusama then most of the defaults should work and the only two values you need to
provided are --csv and --suri like so:

`sh
yarn transfer --csv sample.csv --suri 'here is my mnemonic that I keep very safe because it holds the funds'
`

Force Transfers (On Kusama)

$3

`sh
Usage: force-transfers [options]

Options:
--csv A CSV file formatted , on each line.
--source The address from which funds will be force transferred from.
--cryptoType One of ed25519 or sr25519. (default: "sr25519")
--wsEndpoint The endpoint of the WebSockets to connect with. (default: "wss://canary-4.kusama.network")
--mnemonic Pass in the mnemonic for the Sudo key.
--suri Pass in the suri for the Sudo key.
--jsonPath Pass in the path to the JSON keystore for the Sudo key.
-h, --help output usage information
`

Batch-Proxy-Sudo-Force-Transfers

`zsh
Usage: index batch-proxy-sudo-force-transfers [options]

Options:
--cryptoType One of ed25519 or sr25519. (default: "sr25519")
--csv One or more CSV files formatted , on each line.
--dry Runs in dry run mode.
--source The address from which funds will be force transferred from.
--suri Pass in the suri for the Sudo key.
--types A JSON configuration of types for the node. (default: "{}")
--wsEndpoint The endpoint of the WebSockets to connect with. (default: "wss://canary-4.kusama.network")
-h, --help display help for command
`

$3

`zsh
ts-node src/index batch-proxy-sudo-force-transfers --csv dot_transfers.csv --source 15oF4uVJwmo4TdGW7VfQxNLavjCXviqxT9S1MgbjMNHr6Sp5 --suri --wsEndpoint ws://localhost:9944
`

Add the --dry flag to the command to run a cost estimation of submitting the transaction.

$3

`sh
$ yarn force-transfers --csv test.csv.example --wsEndpoint ws://localhost:9944 --mnemonic 'one two three four' --source 5GrwvaEF5zXb26Fz9rcQpDWS57CtERHpNehXCPcNoHGKutQY
`

Walkthrough (Ethereum functionality)

This walkthrough will proceed through each of the core utilities of the
Ethereum side of the tool using openethereum v3.0.0. The tool was updated
to separate the signing and the broadcasting functionality so it may work
differently than the behavior you expected in the past.

$3

Set up a new account in the local keystore. For this walkthrough we'll be using
the Goerli test network.

`zsh
openethereum account new --chain goerli
`

Type your password in twice and you will be given a fresh and newly generated
account.

`zsh
Please note that password is NOT RECOVERABLE.
Type password:
Repeat password:
0x5b01b9990cd3d7b4ddaff97665eff702d1ccb2a2
`

Now since we will only be using openethereum for its keystore, we can start
the service using the following flags to disable networking and syncing.

`zsh
openethereum --chain goerli --max-peers 0 --ws-apis all
`

You may need some Goerli eth for the newly generated account, please see the
available options on goerli.net.

$3

Now open a new terminal, we'll be using most of the Ethereum functionality
in injection-tool now to manage our own deployment of a FrozenToken and
Claims contract.

> Note: The instruction below assume you have the injection-tool source code
> locally and that you're using ts-node to run the commands. An alternative
> is to install the injection-tool from NPM with npm i @w3f/injection-tool -g.
> After installing you would replace ts-node src/index in the commands below
> with the injection-tool command.

`zsh
ts-node src/index eth:frozenToken-deploy --nonce 0 --output frozen.raw.tx --owner 0x5b01b9990cd3d7b4ddaff97665eff702d1ccb2a2 --from 0x5b01b9990cd3d7b4ddaff97665eff702d1ccb2a2 --password
`

Now we can submit this to the network using the broadcast command.

`zsh
ts-node src/index eth:broadcast --csv frozen.raw.tx --providerUrl wss://goerli.infura.io/ws/v3/7121204aac9a45dcb9c2cc825fb85159
`

The transaction will be broadcast to the node and the script will wait until
it's mined and a receipt is received. It will then print this receipt to a
receipts file and close the process.

In the receipts file ctrl-f and look for transactionHash copy the hash that's
given there and enter it into a block explorer like Etherscan to see the details. If everything went right, you should see the transaction succeeded.

Now we will deploy the claims contract. From the deployment transaction before
we can grab the address for our token (the "dot indicator") from Etherscan.
Use the address for the --dotIndicator option below.

`zsh
ts-node src/index eth:claims-deploy --nonce 1 --output claims.raw.tx --dotIndicator 0x10068eBE0665BB6d7a58deBB0C1c262849613505 --owner 0x5b01b9990cd3d7b4ddaff97665eff702d1ccb2a2 --from 0x5b01b9990cd3d7b4ddaff97665eff702d1ccb2a2 --password
`

Use the broadcast command like before:

`zsh
ts-node src/index eth:broadcast --csv claims.raw.tx --providerUrl wss://goerli.infura.io/ws/v3/7121204aac9a45dcb9c2cc825fb85159
`

#### Allocations

`zsh
ts-node src/index eth:dot-allocations --nonce 2 --output allocations.raw.tx --csv allocations.csv --frozenToken 0x10068eBE0665BB6d7a58deBB0C1c262849613505 --from 0x5b01b9990cd3d7b4ddaff97665eff702d1ccb2a2 --password
`

and

`zsh
ts-node src/index eth:broadcast --csv allocations.raw.tx --providerUrl wss://goerli.infura.io/ws/v3/7121204aac9a45dcb9c2cc825fb85159
`

#### Amendments

`zsh
ts-node src/index eth:amend --nonce 12 --output amendments.raw.tx --csv amend.csv --claims 0x2f0C597Ce268d8dBFD8a7C33639d34A4bBd1ec41 --from 0x5b01b9990cd3d7b4ddaff97665eff702d1ccb2a2 --password
`

#### Vesting

##### Set vesting

Set vesting can only be called on an address that has not claimed yet, and is
not already vested. If you need to increase the vesting on an account, use
increaseVesting instead.

`zsh
ts-node src/index eth:set-vesting --nonce 13 --output vesting.raw.tx --csv vesting.csv --claims 0x2f0C597Ce268d8dBFD8a7C33639d34A4bBd1ec41 --from 0x5b01b9990cd3d7b4ddaff97665eff702d1ccb2a2 --password
`

##### Increase vesting

`zsh
ts-node src/index eth:increase-vesting --nonce 14 --output incVesting.raw.tx --csv incVesting.csv --claims 0x2f0C597Ce268d8dBFD8a7C33639d34A4bBd1ec41 --from 0x5b01b9990cd3d7b4ddaff97665eff702d1ccb2a2 --password
`

#### Making Claims

`zsh
ts-node src/index eth:make-claims --nonce 15 --output claims.raw.tx --csv claims.csv --claims 0x2f0C597Ce268d8dBFD8a7C33639d34A4bBd1ec41 --from 0x5b01b9990cd3d7b4ddaff97665eff702d1ccb2a2 --password
`

#### Broadcast Batching

You can pass the --batch ` flag to the broadcast transaction.