Alright, good morning, everyone! I hope all is well, with all’y’all!

Let’s look at the next two slides…in this first slide of day 4, we see how Vat1, Alice, injects the message from Alice and as it is inflating from ASN1 DER encoding it’s using the Scope to #realize: in and #virtualize: out. As the FarRefDesc for a ref in a different Vat, an immediate #acceptFrom: is sent with the nonce to connect to Bob from Alice.

Andsowe see the FarRef, held by the eventual message #meet: to Alice, just before the msgsend scheduled and activated to Alice. We pre-retrieved it, though it’s still an E-SSE protocol. Tak.

— Have a good one; keep it, light. Kindly, langohr . .. … ‘…^,^ 🐇🐇🐇🐇🐇🐇

—————

𝙎𝙚𝙣𝙩 𝙛𝙧𝙤𝙢 𝘾𝙖𝙡𝙡𝙞𝙨𝙩𝙤 𝙃𝙤𝙪𝙨𝙚 𝙈𝙤𝙗𝙞𝙡𝙚 :: 𝙙𝙚𝙘𝙚𝙣𝙩𝙧𝙖𝙡𝙞𝙯𝙚𝙙 𝙢𝙤𝙗𝙞𝙡𝙚 𝙝𝙤𝙢𝙚𝙡𝙚𝙨𝙨 𝙨𝙤𝙡𝙪𝙩𝙞𝙤𝙣𝙨

—————

On Oct 13, 2022, at 06:40, rabbit rabbit@callistohouse.org wrote:

Hey. Here’s slides 4 & 5. It’s good to be counting on the odd ones! I wholeheartedly endorse such policy.

The #provideFor: message, sent to Bob for his allowing contact by Alice. The result is a Nonce registration in the NonceLocator. <image0.jpeg>

Soas photo 2 from day 2 shows us the nonce is sent by Carole, so she passes the nonce for Bob’s ref to Alice. Thus Alice can ring up Bob with this secure transfer nonce….. the DeliverMessage CapTP-protocol (VatTP is ParrotTalk v3.8) is sent to Alice with said nonce… <image1.jpeg>

— Have a good one; keep it, light. Kindly, langohr . .. … ‘…^,^ 🐇🐇🐇🐇🐇🐇

—————

𝙎𝙚𝙣𝙩 𝙛𝙧𝙤𝙢 𝘾𝙖𝙡𝙡𝙞𝙨𝙩𝙤 𝙃𝙤𝙪𝙨𝙚 𝙈𝙤𝙗𝙞𝙡𝙚 :: 𝙙𝙚𝙘𝙚𝙣𝙩𝙧𝙖𝙡𝙞𝙯𝙚𝙙 𝙢𝙤𝙗𝙞𝙡𝙚 𝙝𝙤𝙢𝙚𝙡𝙚𝙨𝙨 𝙨𝙤𝙡𝙪𝙩𝙞𝙤𝙣𝙨

—————

...

...

On Oct 12, 2022, at 07:30, rabbit rabbit@callistohouse.org wrote:

 Carol sends a message to Alice, Bob as an argument.

<image0.jpeg>

A secure #provideFor:/#acceptFrom: transfer, Bob to Alice is initiated, through Bob…with a shared nonce. <image1.jpeg>

— Have a good one; keep it, light. Kindly, rabbit . .. … ‘…^,^ 🐇🐇🐇🐇🐇🐇

<𝙃𝙖𝙨𝙝𝙏𝙖𝙜: #SqueakEazy> <𝙃𝙖𝙨𝙝𝙏𝙖𝙜: #SquEzy> < 𝙃𝙖𝙨𝙝𝙏𝙖𝙜: #SqWillSqWallSqWay> ———- #SqueakEazy “(…𝙛𝙤𝙧𝙩𝙝𝙘𝙤𝙢𝙞𝙣𝙜 𝙢𝙚𝙩𝙖𝙫𝙚𝙧𝙨𝙚…)”

---

“ 𝐁𝐨𝐨𝐭𝐬𝐚𝐭𝐫𝐚𝐩” <#𝐒𝐪𝐮𝐞𝐚𝐤𝐄𝐚𝐳𝐲𝗜𝗶𝗻𝘀𝘁𝗮𝗻𝘁𝗜𝗶𝗮𝘁𝗜𝗶𝗻𝗴𝗣𝗲𝗻𝗱𝗜𝗶𝗻𝗴> “𝗥𝗲𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗻𝗴 𝘁𝗵𝗲 𝗦𝗶𝘀𝘁𝗲𝗿𝘀” <#𝑫𝒊𝒆𝑨𝒏𝒇𝒖̈𝒉𝒓𝒆𝒓𝗞𝗼𝗻𝘁𝗿𝗼𝗹𝗹𝗶𝗲𝗿𝘁𝗔𝗹𝗹𝗲𝘀 . .. …. ‘…^,^> <#𝑫𝒊𝒆𝑨𝒏𝒇𝒖̈𝒉𝒓𝒆𝒓𝗞𝗼𝗻𝘁𝗿𝗼𝗹𝗹𝗶𝗲𝗿𝘁𝗔𝗹𝗹𝗲𝘀 . .. …. ‘…^,^> <#𝑫𝒊𝒆𝑨𝒏𝒇𝒖̈𝒉𝒓𝒆𝒓𝗞𝗼𝗻𝘁𝗿𝗼𝗹𝗹𝗶𝗲𝗿𝘁𝗔𝗹𝗹𝗲𝘀 . .. …. ‘…^,^> —————

𝙒𝙝𝙚𝙧𝙚’𝙨 𝙒𝙤𝙤𝙙𝙮 𝙛𝙧𝙤𝙢 𝙢𝙖𝙧𝙠𝙚𝙩𝙞𝙣𝙜? ^,^

—————

𝙎𝙚𝙣𝙩 𝙛𝙧𝙤𝙢 𝘾𝙖𝙡𝙡𝙞𝙨𝙩𝙤 𝙃𝙤𝙪𝙨𝙚 𝙈𝙤𝙗𝙞𝙡𝙚 :: 𝙙𝙚𝙘𝙚𝙣𝙩𝙧𝙖𝙡𝙞𝙯𝙚𝙙 𝙢𝙤𝙗𝙞𝙡𝙚 𝙝𝙤𝙢𝙚𝙡𝙚𝙨𝙨 𝙨𝙤𝙡𝙪𝙩𝙞𝙤𝙣𝙨

—————

...

...

On Oct 11, 2022, at 08:40, rabbit rabbit@callistohouse.org wrote:

 Here’s the full scenario. Carol introduces Bob to Alice, as an argument within a message sent: Alice meet: <Bob>.

Then Carol sends a message to the Promise from the previous send and that gets forwarded to Bob. All distributed object stitching is unwoven. <image0.jpeg>

<image1.jpeg>

— Have a good one; keep it, light. Kindly, rabbit . .. … ‘…^,^ 🐇🐇🐇🐇🐇🐇

<𝙃𝙖𝙨𝙝𝙏𝙖𝙜: #𝙎𝙦𝙪𝙚𝙖𝙠𝙀𝙖𝙯𝙮𝙎𝙦𝙒𝙖𝙮𝙎𝙦𝙒𝙚𝙎𝙦𝙒𝙖𝙡𝙡> ———- #SqueakEazy “(…𝙛𝙤𝙧𝙩𝙝𝙘𝙤𝙢𝙞𝙣𝙜 𝙢𝙚𝙩𝙖𝙫𝙚𝙧𝙨𝙚…)”

---

“ 𝐁𝐨𝐨𝐭𝐬𝐚𝐭𝐫𝐚𝐩” <#𝐒𝐪𝐮𝐞𝐚𝐤𝐄𝐚𝐳𝐲𝗜𝗶𝗻𝘀𝘁𝗮𝗻𝘁𝗜𝗶𝗮𝘁𝗜𝗶𝗻𝗴𝗣𝗲𝗻𝗱𝗜𝗶𝗻𝗴> “𝗥𝗲𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗻𝗴 𝘁𝗵𝗲 𝗦𝗶𝘀𝘁𝗲𝗿𝘀” <#𝑫𝒊𝒆𝑨𝒏𝒇𝒖̈𝒉𝒓𝒆𝒓𝗞𝗼𝗻𝘁𝗿𝗼𝗹𝗹𝗶𝗲𝗿𝘁𝗔𝗹𝗹𝗲𝘀 . .. …. ‘…^,^> <#𝑫𝒊𝒆𝑨𝒏𝒇𝒖̈𝒉𝒓𝒆𝒓𝗞𝗼𝗻𝘁𝗿𝗼𝗹𝗹𝗶𝗲𝗿𝘁𝗔𝗹𝗹𝗲𝘀 . .. …. ‘…^,^> <#𝑫𝒊𝒆𝑨𝒏𝒇𝒖̈𝒉𝒓𝒆𝒓𝗞𝗼𝗻𝘁𝗿𝗼𝗹𝗹𝗶𝗲𝗿𝘁𝗔𝗹𝗹𝗲𝘀 . .. …. ‘…^,^> —————

𝙒𝙝𝙚𝙧𝙚’𝙨 𝙒𝙤𝙤𝙙𝙮 𝙛𝙧𝙤𝙢 𝙢𝙖𝙧𝙠𝙚𝙩𝙞𝙣𝙜? ^,^

—————

𝙎𝙚𝙣𝙩 𝙛𝙧𝙤𝙢 𝘾𝙖𝙡𝙡𝙞𝙨𝙩𝙤 𝙃𝙤𝙪𝙨𝙚 𝙈𝙤𝙗𝙞𝙡𝙚 :: 𝙙𝙚𝙘𝙚𝙣𝙩𝙧𝙖𝙡𝙞𝙯𝙚𝙙 𝙢𝙤𝙗𝙞𝙡𝙚 𝙝𝙤𝙢𝙚𝙡𝙚𝙨𝙨 𝙨𝙤𝙡𝙪𝙩𝙞𝙤𝙣𝙨

—————

I'm curious as to what these messages are all about?

On Sat, Oct 15, 2022 at 4:06 PM rabbit rabbit@callistohouse.org wrote:

For the direct message to the esseObject, #doesNotUnderstand: does and eventualSend and returns the promise.

Here, the messageSend #meet: activates in Alice. The EFar to Bob is now within Alice’s #activated #meet: method.

[image: image0.jpeg]

Andsonow we see Alice has sent a messageSend of her own to Bob. Presumably a ##greet: message. The return from Alice’s #meet: activation has returned with the promise from the #greet: call to Bob, and so the resolver from the #meet: send is resolved to this newly remote promise to Bob….whatch, ya see the resolver as the continuation of the #greet: message… [image: image1.jpeg]

— Have a good one; keep it, light. Kindly, langohr . .. … ‘…^,^ 🐇🐇🐇

Sent from Callisto House Mobile - Europa :: decentralized mobile homeless solutions ::

On Oct 14, 2022, at 05:37, rabbit rabbit@callistohouse.org wrote:

Alright, good morning, everyone! I hope all is well, with all’y’all!

Let’s look at the next two slides…in this first slide of day 4, we see how Vat1, Alice, injects the message from Alice and as it is inflating from ASN1 DER encoding it’s using the Scope to #realize: in and #virtualize: out. As the FarRefDesc for a ref in a different Vat, an immediate #acceptFrom: is sent with the nonce to connect to Bob from Alice. <image0.jpeg>

Andsowe see the FarRef, held by the eventual message #meet: to Alice, just before the msgsend scheduled and activated to Alice. We pre-retrieved it, though it’s still an E-SSE protocol. Tak. <image1.jpeg>

— Have a good one; keep it, light. Kindly, langohr . .. … ‘…^,^

🐇🐇🐇🐇🐇🐇

—————

𝙎𝙚𝙣𝙩 𝙛𝙧𝙤𝙢 𝘾𝙖𝙡𝙡𝙞𝙨𝙩𝙤 𝙃𝙤𝙪𝙨𝙚 𝙈𝙤𝙗𝙞𝙡𝙚 :: 𝙙𝙚𝙘𝙚𝙣𝙩𝙧𝙖𝙡𝙞𝙯𝙚𝙙 𝙢𝙤𝙗𝙞𝙡𝙚 𝙝𝙤𝙢𝙚𝙡𝙚𝙨𝙨 𝙨𝙤𝙡𝙪𝙩𝙞𝙤𝙣𝙨

—————

On Oct 13, 2022, at 06:40, rabbit rabbit@callistohouse.org wrote:

Hey. Here’s slides 4 & 5. It’s good to be counting on the odd ones! I wholeheartedly endorse such policy.

The #provideFor: message, sent to Bob for his allowing contact by Alice. The result is a Nonce registration in the NonceLocator. <image0.jpeg>

Soas photo 2 from day 2 shows us the nonce is sent by Carole, so she passes the nonce for Bob’s ref to Alice. Thus Alice can ring up Bob with this secure transfer nonce….. the DeliverMessage CapTP-protocol (VatTP is ParrotTalk v3.8) is sent to Alice with said nonce… <image1.jpeg>

— Have a good one; keep it, light. Kindly, langohr . .. … ‘…^,^

🐇🐇🐇🐇🐇🐇

—————

𝙎𝙚𝙣𝙩 𝙛𝙧𝙤𝙢 𝘾𝙖𝙡𝙡𝙞𝙨𝙩𝙤 𝙃𝙤𝙪𝙨𝙚 𝙈𝙤𝙗𝙞𝙡𝙚 :: 𝙙𝙚𝙘𝙚𝙣𝙩𝙧𝙖𝙡𝙞𝙯𝙚𝙙 𝙢𝙤𝙗𝙞𝙡𝙚 𝙝𝙤𝙢𝙚𝙡𝙚𝙨𝙨 𝙨𝙤𝙡𝙪𝙩𝙞𝙤𝙣𝙨

—————

On Oct 12, 2022, at 07:30, rabbit rabbit@callistohouse.org wrote:

 Carol sends a message to Alice, Bob as an argument.

<image0.jpeg>

A secure #provideFor:/#acceptFrom: transfer, Bob to Alice is initiated, through Bob…with a shared nonce. <image1.jpeg>

— Have a good one; keep it, light. Kindly, rabbit . .. … ‘…^,^

🐇🐇🐇🐇🐇🐇

<𝙃𝙖𝙨𝙝𝙏𝙖𝙜: #SqueakEazy> <𝙃𝙖𝙨𝙝𝙏𝙖𝙜: #SquEzy> < 𝙃𝙖𝙨𝙝𝙏𝙖𝙜: #SqWillSqWallSqWay> ———- #SqueakEazy “(…𝙛𝙤𝙧𝙩𝙝𝙘𝙤𝙢𝙞𝙣𝙜 𝙢𝙚𝙩𝙖𝙫𝙚𝙧𝙨𝙚…)”

---

“ 𝐁𝐨𝐨𝐭𝐬𝐚𝐭𝐫𝐚𝐩” <#𝐒𝐪𝐮𝐞𝐚𝐤𝐄𝐚𝐳𝐲𝗜𝗶𝗻𝘀𝘁𝗮𝗻𝘁𝗜𝗶𝗮𝘁𝗜𝗶𝗻𝗴𝗣𝗲𝗻𝗱𝗜𝗶𝗻𝗴> “𝗥𝗲𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗻𝗴 𝘁𝗵𝗲 𝗦𝗶𝘀𝘁𝗲𝗿𝘀” <#𝑫𝒊𝒆𝑨𝒏𝒇𝒖̈𝒉𝒓𝒆𝒓𝗞𝗼𝗻𝘁𝗿𝗼𝗹𝗹𝗶𝗲𝗿𝘁𝗔𝗹𝗹𝗲𝘀 . .. …. ‘…^,^> <#𝑫𝒊𝒆𝑨𝒏𝒇𝒖̈𝒉𝒓𝒆𝒓𝗞𝗼𝗻𝘁𝗿𝗼𝗹𝗹𝗶𝗲𝗿𝘁𝗔𝗹𝗹𝗲𝘀 . .. …. ‘…^,^> <#𝑫𝒊𝒆𝑨𝒏𝒇𝒖̈𝒉𝒓𝒆𝒓𝗞𝗼𝗻𝘁𝗿𝗼𝗹𝗹𝗶𝗲𝗿𝘁𝗔𝗹𝗹𝗲𝘀 . .. …. ‘…^,^> —————

𝙒𝙝𝙚𝙧𝙚’𝙨 𝙒𝙤𝙤𝙙𝙮 𝙛𝙧𝙤𝙢 𝙢𝙖𝙧𝙠𝙚𝙩𝙞𝙣𝙜? ^,^

—————

𝙎𝙚𝙣𝙩 𝙛𝙧𝙤𝙢 𝘾𝙖𝙡𝙡𝙞𝙨𝙩𝙤 𝙃𝙤𝙪𝙨𝙚 𝙈𝙤𝙗𝙞𝙡𝙚 :: 𝙙𝙚𝙘𝙚𝙣𝙩𝙧𝙖𝙡𝙞𝙯𝙚𝙙 𝙢𝙤𝙗𝙞𝙡𝙚 𝙝𝙤𝙢𝙚𝙡𝙚𝙨𝙨 𝙨𝙤𝙡𝙪𝙩𝙞𝙤𝙣𝙨

—————

On Oct 11, 2022, at 08:40, rabbit rabbit@callistohouse.org wrote:

 Here’s the full scenario. Carol introduces Bob to Alice, as an argument within a message sent: Alice meet: <Bob>.

Then Carol sends a message to the Promise from the previous send and that gets forwarded to Bob. All distributed object stitching is unwoven. <image0.jpeg>

<image1.jpeg>

— Have a good one; keep it, light. Kindly, rabbit . .. … ‘…^,^

🐇🐇🐇🐇🐇🐇

<𝙃𝙖𝙨𝙝𝙏𝙖𝙜: #𝙎𝙦𝙪𝙚𝙖𝙠𝙀𝙖𝙯𝙮𝙎𝙦𝙒𝙖𝙮𝙎𝙦𝙒𝙚𝙎𝙦𝙒𝙖𝙡𝙡> ———- #SqueakEazy “(…𝙛𝙤𝙧𝙩𝙝𝙘𝙤𝙢𝙞𝙣𝙜 𝙢𝙚𝙩𝙖𝙫𝙚𝙧𝙨𝙚…)”

---

“ 𝐁𝐨𝐨𝐭𝐬𝐚𝐭𝐫𝐚𝐩” <#𝐒𝐪𝐮𝐞𝐚𝐤𝐄𝐚𝐳𝐲𝗜𝗶𝗻𝘀𝘁𝗮𝗻𝘁𝗜𝗶𝗮𝘁𝗜𝗶𝗻𝗴𝗣𝗲𝗻𝗱𝗜𝗶𝗻𝗴> “𝗥𝗲𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗻𝗴 𝘁𝗵𝗲 𝗦𝗶𝘀𝘁𝗲𝗿𝘀” <#𝑫𝒊𝒆𝑨𝒏𝒇𝒖̈𝒉𝒓𝒆𝒓𝗞𝗼𝗻𝘁𝗿𝗼𝗹𝗹𝗶𝗲𝗿𝘁𝗔𝗹𝗹𝗲𝘀 . .. …. ‘…^,^> <#𝑫𝒊𝒆𝑨𝒏𝒇𝒖̈𝒉𝒓𝒆𝒓𝗞𝗼𝗻𝘁𝗿𝗼𝗹𝗹𝗶𝗲𝗿𝘁𝗔𝗹𝗹𝗲𝘀 . .. …. ‘…^,^> <#𝑫𝒊𝒆𝑨𝒏𝒇𝒖̈𝒉𝒓𝒆𝒓𝗞𝗼𝗻𝘁𝗿𝗼𝗹𝗹𝗶𝗲𝗿𝘁𝗔𝗹𝗹𝗲𝘀 . .. …. ‘…^,^> —————

𝙒𝙝𝙚𝙧𝙚’𝙨 𝙒𝙤𝙤𝙙𝙮 𝙛𝙧𝙤𝙢 𝙢𝙖𝙧𝙠𝙚𝙩𝙞𝙣𝙜? ^,^

—————

𝙎𝙚𝙣𝙩 𝙛𝙧𝙤𝙢 𝘾𝙖𝙡𝙡𝙞𝙨𝙩𝙤 𝙃𝙤𝙪𝙨𝙚 𝙈𝙤𝙗𝙞𝙡𝙚 :: 𝙙𝙚𝙘𝙚𝙣𝙩𝙧𝙖𝙡𝙞𝙯𝙚𝙙 𝙢𝙤𝙗𝙞𝙡𝙚 𝙝𝙤𝙢𝙚𝙡𝙚𝙨𝙨 𝙨𝙤𝙡𝙪𝙩𝙞𝙤𝙣𝙨

—————