Michael FIG

> reserve a port number and host at `127.0.0.1:$PORT/$NONCE/` That would be acceptable.

> Maybe that should even be expressible with a different kind of dot in dotted paths. A different kind of dot means that petnames can't be a subset of JavaScript....

> a deconstructable global `HandledPromise` (e.g., even `globalThis.HandledPromise = false` suffices) I'm confused as to what `@endo/marshal` buys us in isolation. For "terminating CapTP", all we need are functioning versions...

> I assume that's not possible to ponyfill (is it?). The problem with not installing `HandledPromise` (or its spiritual successors) somewhere in `globalThis` is that it really needs a few...

Sorry for the long delay, @dead-claudia. That was a lot to digest, and I'm still trying to analyse the gaps between what you have here and what our designs have...

One minor correction. > The first case has to necessarily wait for the promise to resolve, but the current eventual send proposal also forces the second to wait for the...

I like `const delpromise = Promise.createDelegated(promise, delegation)` as an API. I think my concerns can be solved by adjusting `Promise.delegate(...)` to enforce a turn boundary before touching `delegation`. As an...

I'd like to invite comments on a [slideshow of my suggestions for an Eventual Send API Redesign](https://docs.google.com/presentation/d/17xazO_BljV3MZwGKsVmWXzmIdDMPxoJeb81AczYxSis/edit?usp=sharing) inspired by the discussion in this issue. If access permits you, you can...

> I'm not sure that should be a consideration - the identity of individual promises is not very reliable due to frequent use of `await` and `Promise.resolve` (and all the...

I may have explained this badly. But the need for serialisation and still preventing premature GC of the promise is the motivator.