11 May 2023 |
sickpig | In reply to @nyusternie:matrix.org
sickpig: i see that Rostrum 8.1 has been pushed to crates.io 👍️
could you breakdown the hex being returned in the new https://bitcoinunlimited.gitlab.io/rostrum/protocol/methods/#blockchainblockget
or more specifically, how is this different from blockchain.block.headers ??
Will have a look at it tomorrow | 19:05:30 |
13 May 2023 |
| kume00#3041 changed their display name from kume001#3041 to kume00#3041. | 17:56:38 |
| kume00#3041 removed their profile picture. | 17:56:40 |
16 May 2023 |
Shomari | sickpig: while running some tests on the NexaJS wallet class, I constructed this tx which was successfully broadcasted via Rostrum (without a fee) https://explorer.nexa.org/tx/39cc671f49431201fd0a6c47c78fa5d80d11a8df229ce20ff227b68f26adbd2b | 22:12:29 |
Shomari | if i use sendrawtransaction directly from the node, then I receive:
error code: -26
error message:
66: mempool min fee not met
| 22:12:52 |
Shomari | i'm wondering why Rostrum doesn't return that error?? 🤔 | 22:13:16 |
Andrew Stone | interesting | 22:17:47 |
Andrew Stone | hey do you know about "./nexa-cli validaterawtransaction"? | 22:18:02 |
Andrew Stone | can you write a bug in Rostrum here: https://gitlab.com/bitcoinunlimited/rostrum/-/issues | 22:19:12 |
Andrew Stone | I have a theory which is that in Bitcoin days you could push a tx directly into the mempool overriding any fee calc because you were assumed to know what you were doing if you were using the RPC interface. Maybe Rostrum is still using an API into nexad that does that. But it probably shouldn't | 22:20:26 |
Andrew Stone | (I'm not seeing your tx on my node either so it (properly) did not propagate) | 22:20:54 |
Andrew Stone | (sorry, gtg) | 22:21:01 |
Shomari | In reply to @andrewstone:matrix.org hey do you know about "./nexa-cli validaterawtransaction"? I've never used it before until now .. interesting | 22:24:31 |
Shomari | In reply to @andrewstone:matrix.org can you write a bug in Rostrum here: https://gitlab.com/bitcoinunlimited/rostrum/-/issues sure | 22:25:01 |
Shomari | https://gitlab.com/bitcoinunlimited/rostrum/-/issues/192 | 22:37:58 |
17 May 2023 |
sickpig | In reply to @nyusternie:matrix.org i'm wondering why Rostrum doesn't return that error?? 🤔 This is due to the fact that I was asked to configure the node behind the explorer in such a way to accept 0 fee transactions
If you have used the rostrum instance linked to that node this is why it got accepted
Sorry for the inconvenience | 06:19:17 |
Shomari | no inconvenience lol .. thanks for the clarification | 08:25:53 |
Shomari | I'll run some tests against my own Rostrum node later today; then close that issue if all is well 😉 | 08:28:33 |
20 May 2023 |
| @ralph:fx45.in left the room. | 22:29:27 |
22 May 2023 |
| Skinned#9273 changed their display name from Skinned to Skinned#9273. | 11:01:48 |
23 May 2023 |
| JrD#4541 changed their display name from JrD to JrD#4541. | 09:05:40 |
| All B#7694 changed their profile picture. | 10:52:57 |
26 May 2023 |
| Mild#6669 changed their display name from MildHigh#6669 to Mild#6669. | 01:05:00 |
| Mild#6669 changed their profile picture. | 01:05:05 |
31 May 2023 |
Shomari | hey Andrew Stone i sent u dm last week wrt the multi-sig examples you provided to me earlier .. i'm very close, but I'm stuck on one thing (that I've so far identified) .. how do i generate the "Output constraint" from the "redeemscript" ?? | 22:13:57 |
Shomari | based on the example values you provided, how do I convert:
522102bd13fc253edbcbcbfa1c21b7ba63336c30dbd3b51bdb4deb3e28547d7c1dd4762103802a8952f26f69fdd2301c7f91571f56165ba8af5dc0f5272ae23af226774856210293112f13c7295880317a16e8b8552e8d5d3fc9ff28bdade2e9532ffa063928cd53af
into
0014691bc2935439e924ca8cae5d7b97c35f8eccfbd500 ?
| 22:14:48 |
Shomari | sickpig jQrgen ▽ any idea how to convert from a redeem script to the equivalent of a public key hash script? | 22:17:42 |
Shomari | the 00 s on either end are a bit confusing to me as well .. if someone could explain how/why that works, would be much appreciated 🙏 | 22:19:19 |
1 Jun 2023 |
| QUIT#5070 changed their display name from Mfahham ⛛#5070 to QUIT#5070. | 11:31:57 |
| QUIT#5070 changed their profile picture. | 11:31:59 |