WindKit v0.2.1 – PeerJS Standalone

WindKit v0.2.1 – PeerJS Standalone

This release adds a fully standalone PeerJS connection layer so Vexanium DApps can connect to the Wind Wallet out-of-the-box—no environment variables required. Defaults match Wind’s production signaling stack.

---

✨ What’s new

• PeerJS defaults (standalone)
  • host=core.windcrypto.com, port=443, secure=true, path='/', key='peerjs'
• Server config helpers
  • configureForCore()
  • setServer(host, { port, secure, path, key }), setPath(), setKey(), setSecure(), setPort()
• ICE / TURN utilities
  • addIceServer(), setIceServers(), clearIceServers()
  • Validation rejects turn:/turns: entries without username & credential
• Events
  • Re-emits: open, close, disconnected, error, plus wallet session
• Session persistence
  • Reuses valid sessions via sessionStorage (exp and sig)

🛠 Improvements & fixes

• Full TypeScript refactor with dual outputs (ESM dist/index.js, CJS dist/index.cjs) and dist/index.d.ts
• More reliable re-login flow; expired sessions are auto-cleared
• Prevents WebRTC error: “Both username and credential are required when the URL scheme is turn/turns.”

---

⚡ Quick start

import { WindConnector } from "windkit";

const connector = new WindConnector();            // defaults already target core.windcrypto.com
const vsr = connector.createLoginRequest("Wind DApp", "https://example.com/icon.png");

connector.on("session", (session) => {
  console.log("Connected:", session.actor?.toString());
});

await connector.connect();

// Deep-link (optional):
// https://wallet.windcrypto.com/login?vsr=<request>

WindKit v0.1.1 – Initial Release

First public release of WindKit, a protocol for connecting Vexanium DApps to the Wind wallet, enabling secure communication and transaction signing.

Features

• Cross-device login via VSR (Vexanium Signing Request)
• Transaction signing (single/multi-action)
• Message signing
• Shared secret (ECDH) for encryption
• PeerJS-based WebRTC signaling

Docs

• npm: https://www.npmjs.com/package/windkit
• See README.md for usage examples.