Consider updating ergo-node-interface about oracle-core

[greenhat]

Good catch! I'm also testing bootstrap on the testnet. I fixed it in ergoplatform/ergo-node-interface-rust#11 and will merge it ASAP. What newer versions do you mean?

[greenhat]

If by the newer version you mean my PR, then yes, please send a PR to update it here in develop branch.

[SethDusek]

I believe latest develop branch (ergo-node-interface) does not have this issue, while the one oracle-core has pinned to has the outdated serialization. I'm currently working on an update.

I ran into some additional issues in the bootstrap phase. I'll try to take a look at those as well

Currently running into this after getting the previous issue fixed:

2022-07-05T10:57:40.963260355+05:00 INFO oracle_core::cli_commands::bootstrap - bootstrap.yaml loaded
2022-07-05T10:57:40.989778157+05:00 INFO oracle_core::cli_commands::bootstrap - Minting pool NFT tx
2022-07-05T10:57:41.022960102+05:00 INFO oracle_core::cli_commands::bootstrap - Minting refresh NFT tx
2022-07-05T10:57:41.039046012+05:00 ERROR oracle_core - Fatal bootstrap error: node error: The node rejected the request you provided.

I think the issue might be that each step in the bootstrap process uses the UTXOs created by the previous transaction, but those transactions haven't actually been submitted yet, so the node rejects that transaction because it doesn't know about those boxes? If my understanding of the issue is correct, is there any way to build a chained transaction?

[greenhat]

I believe latest develop branch (ergo-node-interface) does not have this issue, while the one oracle-core has pinned to has the outdated serialization.

That's weird. I'm sure it's only fixed in my PR.

I'm currently working on an update.

I ran into some additional issues in the bootstrap phase. I'll try to take a look at those as well

Great! I'm documenting my progress in #61 in comments.

Currently running into this after getting the previous issue fixed:

2022-07-05T10:57:40.963260355+05:00 INFO oracle_core::cli_commands::bootstrap - bootstrap.yaml loaded
2022-07-05T10:57:40.989778157+05:00 INFO oracle_core::cli_commands::bootstrap - Minting pool NFT tx
2022-07-05T10:57:41.022960102+05:00 INFO oracle_core::cli_commands::bootstrap - Minting refresh NFT tx
2022-07-05T10:57:41.039046012+05:00 ERROR oracle_core - Fatal bootstrap error: node error: The node rejected the request you provided.

I think the issue might be that each step in the bootstrap process uses the UTXOs created by the previous transaction, but those transactions haven't actually been submitted yet, so the node rejects that transaction? If my understanding of the issue is correct, is there any way to build a chained transaction?

That's where I'm stuck now as well. Chained tx should work if the inputs are in mempool. Here is the test for this in node - https://github.com/ergoplatform/ergo/blob/205eabf79806b428f86d4b8c866b4df0581b9458/src/test/scala/org/ergoplatform/http/routes/TransactionApiRouteSpec.scala#L64-L78

[greenhat]

Wait, I forgot I have #71
I'm going to merge it ASAP.