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 admittedly 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 analogy is in the event you’re a restaurant prepare dinner that does not have a devoted server. You may opportunistically convey meals to tables if you end cooking them, which is usually wonderful, however you may fall behind throughout rush hour. The ticket system additionally does not rate-limit: when you possibly can’t maintain all of the tickets, random ones fall to the bottom and also you overlook these orders. One annoying buyer can damage others’ eating expertise by ordering 100 food plan cokes.
We will rent one other individual to serve meals, which will definitely make the restaurant extra environment friendly (e.g. BIP 331, nonetheless WIP) however does not resolve every part. From 30.0, we’ll have a technique that rate-limits prospects to make sure we do not overlook anyone’s order except they ship big 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?
An important 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 does not work. This has modified as properly (“bundle validation: loosen up the package-not-child-with-unconfirmed-parents rule” https://github.com/bitcoin/bitcoin/pull/31385).
Bitcoin Core 28.0 will mechanically type a 1p1c bundle after I broadcast transactions through sendrawtransaction
That is right: as soon as you have submitted the transactions to your mempool, nodes will do every part mechanically. If it is a 0-fee dad or mum + baby bundle, sendrawtransaction would possibly complain concerning the charge, so that you would possibly need to use the submitpackage RPC (the multi-transaction equal of sendrawtransaction with a really comparable API). The RPC accepts single transactions as properly, so it could be most handy to make use of on a regular basis.
