What precisely does non-robust imply on this context?
Non-robust means “not assured to work, notably within the presence of adversaries or when quantity is admittedly excessive so we miss issues.” Additionally, “package deal relay” in quotes refers to the truth that there is not a package deal relay protocolsimply 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 when you’re a restaurant cook dinner that does not have a devoted server. You possibly can opportunistically convey meals to tables if you end cooking them, which is commonly effective, however you may 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 neglect these orders. One annoying buyer can destroy others’ eating expertise by ordering 100 weight loss program cokes.
We are able to rent one other individual to serve meals, which will definitely make the restaurant extra environment friendly (e.g. BIP 331, nonetheless WIP) however would not resolve all the things. From 30.0, we’ll have a method that rate-limits clients to make sure we do not neglect anyone’s order until they ship large 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 might nonetheless fail to verify?
Crucial 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 properly (“package deal validation: loosen up the package-not-child-with-unconfirmed-parents rule” https://github.com/bitcoin/bitcoin/pull/31385).
Bitcoin Core 28.0 will routinely type a 1p1c package deal once I broadcast transactions through sendrawtransaction
That is appropriate: as soon as you’ve got submitted the transactions to your mempool, nodes will do all the things routinely. If it is a 0-fee dad or mum + baby package deal, sendrawtransaction may complain concerning the price, so that you may wish to use the submitpackage RPC (the multi-transaction equal of sendrawtransaction with a really related API). The RPC accepts single transactions as properly, so it is perhaps most handy to make use of on a regular basis.
