Neighbor transactions can't be implemented as a mere bit. They have to commit to the transactions they're paying for cryptographically or miners would be able to manipulate them.
Neighbor transactions could be more efficient by committing to multiple transactions at once though, eg "hash the next N txids".
Reverse it, it's still one bit for multiple transactions. "The next tx is committing to me".
Please Login to reply.
Doesn't change anything. The transaction still needs to commit securely.
Sorry, I was assuming that we also changed signature semantics to commit to the prior txids. New tapscript, or new sig opcode.
