I am pasting the solution here that i got as a response from the slack channel, almost verbatim.
By default, EthereumJS-Tx signs for the Ethereum Mainnet. Transactions made for custom networks have some of their values changes, and this needs to be taken into account when signing the transactions. What has happened here is we have signed the transaction ...
This is solved now. There was a tiny bug in the code and in the ethers library that would not correctly return the chainId and calculate the v value. It's fixed now, see here. Many thanks to ricmoo for helping out.
I wrote a gist that correctly recovers the public key given the transaction.
const tx = await provider.getTransaction(...)
You will need to implement a smart contract using something like Solidity.
Please take a look at this if you would like a fairly easy way to learn the basics of Solidity: https://cryptozombies.io/
If the language itself allows you to properly handle and store the types of data in the ways that you need to, we would need to establish whether or not Ethereum ...
Everything (no exceptions) starts with a transaction signed by an externally owned account (EOA).
Signed transactions are sent to the network and included in a block. Blocks establish the canonical transaction order. (Peer discovery, gossip and mining.)
Ordered transactions are processed by nodes as the blocks arrive. To deploy that contract, first, it is ...
Please see my comment for suggestions to get a more informative answer.
How to save the output in a blockchain (on-chain) through transactions?
You pass a signed transaction to a function that is designed to receive the data (arguments) and you store the values in contract state variables.
How to include the On-chain blockchain in all this through ...
The code you pasted is code for creating a smart contract. So that is a program running inside the Ethereum blockchain and users of the blockchain can interact with the smart contract. Everything the contract does happens inside the blockchain.
Now if I just copypaste that code (or any other code to create a smart contract) to some editor it obviously is ...
You can simply deploy them as separate contracts.
On the "DEPLOY & RUN TRANSACTIONS" section of Remix, you can choose which contract you want to deploy, even if they are in the same file.
When you have chosen your contract, simply hit "Deploy" on that same page.
You can choose your network by specifying the "Environment" (on that same page) and ...
So as of Quorum v2.4.0, the underlying geth is still v1.8.x. That means you are a bit limited to the hardforks and EVM changes you may use when using remix and other solidity compilers.
First, you need to ensure that you have all of the supported hard-forks enabled in Quorum genesis, a quick reference is our own quourm-examples project: https://github.com/...
Run it again.
More generally, run it inside a try/catch block until success.
For your specific error, it is possible that the node is not synchronized with your account's current nonce, so you may want to add this to your options object:
nonce: await web3.eth.getTransactionCount(0xYourAccountAddress)
Since you may also encounter other types of errors, I ...