Collections not using psbt workflow #1963
Conversation
Co-authored-by: ericatallah <eric.atallah@gmail.com>
```
error: Failed to send reveal transaction
because: JSON-RPC error: RPC error response: RpcError { code: -26, message: "non-mandatory-script-verify-flag (Invalid Schnorr signature)", data: None }
```
``` thread 'main' panicked at 'signature hash should compute: PrevoutKind', src/subcommand/wallet/inscribe.rs:360:8 ```
reveal TX for inscriptions containing a parent.
Ignore malformed inscriptions. Co-authored-by: Clarke Benedict <clarke.plumo@gmail.com>
Indirect pull from https://github.com/raphjaph/ord/pull/3/commits Props to @ericatallah for contributing this
…into collections-no-psbt
|
@raphjaph You may already be aware but I just wanted to bring to your attention that this branch introduces an inscription numbering inconsistency with master since the child inscriptions are not counted in the current master yet some have already been inscribed. It looks like this is the first child inscription and where the numbers begin to diverge. 420285 |
Yes, see https://github.com/casey/ord/issues/2000 - this is an issue independent of collections. The main branch currently ignored any inscription not on the first input. |
|
Hello, just checking if parent/child inscribing is still on the radar? |
|
Yes, very much still on radar. Will resume once the work on cursed inscriptions is finished. |
No description provided.