Kendall Weihe
Kendall Weihe
@nitro-neal this may be up your alley?
love it @diehuxx! 👍
I'm running into this same issue
I can confirm this behavior is happening to a project of mine as well. @ido1wald seems to be onto something. I'm not handling any events. Anyone has a solution to...
This is not a priority whatsoever as proposed changes could be made without impacting the tbdex protocol version
This made me just question: should we also version the tbdex `http-api` spec? And how would that be implemented? Perhaps we should open a new ticket? Again, not a priority...
> 5. Close message @thehenrytsai does this answer your confusion? https://github.com/TBD54566975/tbdex/issues/257 I'm going to update the spec docs with what's in that ticket, but in different words
> Is the "prior to a Close where the Close.success is true" referring to the FPI's close here? > ...being distinct messages... I think you've hit the nail on the...
Here's how I'm thinking about this... tbdex is not a transaction settlement protocol, it's an exchange protocol which is composed of 2 sequential transactions -- pay-in and pay-out -- both...
Subjective interpretation: - "Dealer" too close to "broker dealer" (AKA too narrow) - "Node" too generic - "Institution" too centralized, but I'm not 100% on this one... could see it...