<p>the original vision was to use Plutus Application Backends, unfortunately the development is lagging behind.</p>
<p>We're still early in the development ecosystem, so what you described is mostly the one we can use for now.</p>

CC BY-SA 4.0
2023-01-13T05:05:44.500Z
Thanks. Good to know. Just wish there is something better already.
Adam
CC BY-SA 4.0
2023-01-09T16:29:12.997Z
2023-01-09T16:29:12.997Z
Cristovao Morgado
<p>Currently my workflow is like this:</p>
<ol>
<li>write a validator script in Plutus</li>
<li>test the script in by creating functions/endpoints to submit transactions to <code>Plutus.Trace</code> (Emulator)</li>
<li>if the test goes well, I serialize the script and get a <code>script.plutus</code> file</li>
<li>test the serialized script in the blockchain (preprod or mainnet) using cardano-cli or other front-end tools (like lucid or mesh)</li>
</ol>
<p>Step 4 is quite laborious. It requires that you find the right syntaxes in the front-end tools that are equivalent to Plutus’ in step 2. You might not find one. Or your tools of choice may not yet support state-of-the-art features your dapp needs. And, of course, if the test fails and the validator script needs changes, you have to go back to step 1. Going through 2-4 all over again.</p>
<p>So I figure: if I can submit transactions to the blockchain right there in Plutus, life will be much easier. That would eliminate step 3-4 and speedup the development immeasurably. That would also reduce bugs and errors when translating between multiple platforms/environments.</p>
<p>Is there a way to achieve that?</p>
<p>Or, is there a better/faster workflow?</p>

<plutus><cardano-cli><plutustx><emulator>
Submit transactions to the blockchain in Plutus
# Submit transactions to the blockchain in Plutus

(Asked by: username_0 on 2022-12-28)

Currently my workflow is like this:

1. write a validator script in Plutus
2. test the script in by creating functions/endpoints to submit transactions to `Plutus.Trace` (Emulator)
3. if the test goes well, I serialize the script and get a `script.plutus` file
4. test the serialized script in the blockchain (preprod or mainnet) using cardano-cli or other front-end tools (like lucid or mesh)

Step 4 is quite laborious. It requires that you find the right syntaxes in the front-end tools that are equivalent to Plutus’ in step 2. You might not find one. Or your tools of choice may not yet support state-of-the-art features your dapp needs. And, of course, if the test fails and the validator script needs changes, you have to go back to step 1. Going through 2-4 all over again.

So I figure: if I can submit transactions to the blockchain right there in Plutus, life will be much easier. That would eliminate step 3-4 and speedup the development immeasurably. That would also reduce bugs and errors when translating between multiple platforms/environments.

Is there a way to achieve that?

Or, is there a better/faster workflow?

**Tags:** plutus, cardano-cli, plutustx, emulator

---

## 1 answers

### Answer by username_1 on 2023-01-09. Score: 1

the original vision was to use Plutus Application Backends, unfortunately the development is lagging behind.

We're still early in the development ecosystem, so what you described is mostly the one we can use for now.

> **Comments:**
> **username_0**: Thanks. Good to know. Just wish there is something better already.  

---

