Feature request: aiken deploy

[MartinSchere]

What is your idea? Provide a use case.

Provide a command aiken deploy to "deploy" validators. This command would create a transaction outputting an unspendable UTxO with the script and print the reference to the console.

Why is it a good idea?

Using reference scripts is an obvious default, as attaching them in every transaction is highly inefficient. Because this is the most common practice and a necessary step in the flow, this will save time for every developer using Aiken.

What is the current alternative and why is it not good enough?

The current alternative is cumbersome: Create a wallet, fund it, create a lucid script, build and submit the transaction. This idea is borrowed from Truffle (EVM), and it saves all that process.

[rvcas]

@MartinSchere converted to a discussion until we nail down some deliverables or decide it's not worth it.

Do you have something more specific in mind? What parts of the current alternative would this cover?

I could see it removing the need to

• create a lucid script
• build the transaction

So that said, I'm not exactly sure if we want to implement wallet features and usually wallets have submission covered.

How else would we do this without a wallet somehow? Or how do you see the wallet being involved for this feature?

[micahkendall]

We could add a disposable hot wallet to translucent which displays an address to fund, polls for sufficient funds to receive, executes a deployment defined by a builder pattern, refunds any change back to you once deployment is complete.

(I don't have time anywhere soon for this)

Alternatively to the hot wallet idea, run a web-server and use CIP-30 to fund the build. Then it's more deterministic.