The NEAR Urbit object's poke() method should still take an agent, a mark, and some data, but rather than using those directly as the parameters for the wrapped urbit.poke(), hardcode in the agent and mark fields to point at %near-handler, and send the data as [%poke agent mark data]. %near-handler will then take use this data to construct a poke to the true receiving agent.
Demo: an Urbit app, written using the forked NEAR Social VM library, that simply displays a blank page and prints a message in dojo (or adds a pal, or something else trivial) via %near-handler.
bonbud-macryg
commented
9 months ago
Prerequisites: #1 and #2
The NEAR Urbit object's
poke()method should still take an agent, a mark, and some data, but rather than using those directly as the parameters for the wrappedurbit.poke(), hardcode in the agent and mark fields to point at%near-handler, and send the data as[%poke agent mark data].%near-handlerwill then take use this data to construct a poke to the true receiving agent.Demo: an Urbit app, written using the forked NEAR Social VM library, that simply displays a blank page and prints a message in dojo (or adds a pal, or something else trivial) via %near-handler.