Pyre

One session, one key, one deletion

[Pyre @PyreScope]

$PYRE is live on NEAR.

One session. One key. One deletion.

CA: pyre-4.nearlytrade.near

https://t.co/kmT8ol8fPC

[Pyre @PyreScope]

ca update.

[Pyre @PyreScope]

Locking $PYRE supply now!

[Pyre @PyreScope]

Join $PYRE channel: https://t.co/R4zQyKekzc

[Pyre @PyreScope]

Let's go $PYRE time.

https://t.co/kmT8ol8fPC

[Pyre @PyreScope]

Ready for $PYRE?

The scope is set. The next session begins soon.

One session. One key. One deletion.

NEAR, stay close.

[Pyre @PyreScope]

The Pyre Scope console is open.

Explore scoped keys for perp sessions on NEAR. Define the permissions, use the key within its limits, then burn it on exit.

One session. One key. One deletion.

https://t.co/NjEoac9pM7

[Pyre @PyreScope]

Why does Pyre Scope end with a burn?

Because ending a session should include ending its key’s access
Our introduction walks through the full cycle: scope, session, deletion, and the record left behind

[Pyre @PyreScope]

https://t.co/GePabIbRPP

[Pyre @PyreScope]

A session key should have a clear boundary

Pyre Scope lets you define the contract and permitted methods before the session begins

The key gets its scope
You decide when its access ends

[Pyre @PyreScope]

https://t.co/GePabIbRPP

[Pyre @PyreScope]

Every session begins with a fresh key
Every exit ends with a burn

Meet Pyre Scope: define the scope, use the key within its limits, then delete it when the session ends

One session. One key. One deletion

Built for @NEARProtocol