Improve the fueling of a node

[pgrange]

One important for a node before being able to participate in a head is to mark some UTxO as fuel.

I don't know if we would drop this fueling step in the future but, anyway, we should improve the user experience with this step.

Why

It's important that we give an as best as possible user experience. We can see in #548 a user struggling on how to fuel their node.

Today, we have several fueling scripts available and they are all tied to one or another deployment sample:

• The demo does fueling in a way
• The gcp sample seems to have two scripts to do it, create-marker-utxo.sh and fuel-testnet.sh
• We have some testnet setup that uses also two scripts that seem to do it, fuel-testnet.sh and squash-utxo.sh
• Yet another script is used by the aws sample
• In the wild we find other scripts to fuel a node

We should help our users to fuel their node easily, whatever deployment the chose.

What

Not sure what we should do. If fueling is something that will be part of hydra in long run, we should probably provide a binary that just does that, maybe in the form of a hydra-cli command?

[ch1bo]

Nice write-up of the situation!

[pgrange]

While doing this, I also suggest we take a look at the other squash-utxo script as it would probably be needed by a user at some point then they are playing with hydra.

[ghost]

How about extending hydra-tools which is a swissknife executable for doing various operations with Hydra?

[ch1bo]

Or implement https://github.com/input-output-hk/hydra/issues/215 which will make the distinction of fuel and other UTxO redundant.

[ch1bo]

Since #924 the scripts mentioned in this issue should not be needed anymore.