What precisely does non-robust imply on this context?
Non-robust means “not assured to work, significantly within the presence of adversaries or when quantity is basically excessive so we miss issues.” Additionally, “bundle relay” in quotes refers to the truth that there is not a bundle relay protocol, simply an opportunistic piece of logic that may see when an orphanage transaction occurs to be CPFPing a transaction that failed for being low feerate.
Maybe a superb analogy is when you’re a restaurant cook dinner that does not have a devoted server. You’ll be able to opportunistically deliver meals to tables if you end cooking them, which is commonly effective, however you will fall behind throughout rush hour. The ticket system additionally would not rate-limit: when you’ll be able to’t maintain all of the tickets, random ones fall to the bottom and also you overlook these orders. One annoying buyer can wreck others’ eating expertise by ordering 100 eating regimen cokes.
We will rent one other particular person to serve meals, which will definitely make the restaurant extra environment friendly (e.g. BIP 331, nonetheless WIP) however would not clear up the whole lot. From 30.0, we’ll have a method that rate-limits clients to make sure we do not overlook anyone’s order except they ship enormous volumes (see “p2p: enhance TxOrphanage denial of service bounds” https://github.com/bitcoin/bitcoin/pull/31829).
Are there conditions the place my dad or mum transaction may nonetheless fail to verify?
A very powerful restriction in 28.0 is that cooks can solely serve quite simple issues (1p1c packages). Nothing past 1p1c works. If the kid has one other unconfirmed dad or mum, even when it is already in mempools, the opportunistic logic would not work. This has modified as nicely (“bundle validation: chill out the package-not-child-with-unconfirmed-parents rule” https://github.com/bitcoin/bitcoin/pull/31385).
Bitcoin Core 28.0 will routinely type a 1p1c bundle once I broadcast transactions through sendrawtransaction
That is appropriate: as soon as you have submitted the transactions to your mempool, nodes will do the whole lot routinely. If it is a 0-fee dad or mum + baby bundle, sendrawtransaction would possibly complain concerning the price, so that you would possibly need to use the submitpackage RPC (the multi-transaction equal of sendrawtransaction with a really related API). The RPC accepts single transactions as nicely, so it could be most handy to make use of on a regular basis.
