[2508 Grant Proposal] Winks.fun: On-chain actions on Rootstock within Twitter

Grants & Incentives
1

  1. Project Name & Description
    Winks.fun: Turn tweets into transactions. Winks let users mint, swap, and stake directly inside Twitter. Winks are Twitter-native apps that let users perform end-to-end on-chain transactions (mint, swap, stake, bridge, etc.) directly inside tweets. They eliminate friction, increase conversion, and engage users without redirecting them to external dApps. Think of them as embedded portals to the blockchain, inside the world’s most active crypto community platform.

    Winks ease onboarding of Crypto Twitter to Rootstock and its dapps by making Web3 accessible where users already are: inside Twitter. No redirects. No drop-offs. Just pure, embedded on-chain action.

  2. Team Background
    Jonah Schulman, Contributor & Advisor: Strategic leader with 8+ years of experience across crypto, tokenization, privacy tech, and DeFi. Track record of driving 7-figure capital raises, 20M+ media impressions, and scaling Web3 integrations and user growth. Ex-Security Token Market, ex-Arca, ex-Tokeny, and ex-Singularity. LI: “jonahschulman”

    Atharva Sabnis, Core Contributor: 9+ years of experience in SaaS, AI, and building scalable software startups. Alumni of the Rochester Institute of Technology, Fellow at DraperU, Antler Singapore, and HadronFC by Polygon Ventures. ex-IN-D.ai, ex-Eugenie AI, ex-NFT Labs. LI: ”atharvasabnis”

    Ayan Uali, Technical Contributor: Ex Senior Engineer @ Fortune 500 companies; full-stack software engineer. Alum of the Rochester Institute of Technology, Fellow of Antler Singapore. Ex-Fidelity, ex-NFT Labs. GH: “ayanuali”

    Thiru M, Technical Contributor: Award-winning web3 developer with 5+ years experience with web3 companies such as StarkShooter, SecureDapp, Rariko, and GigsHub. Winner of multiple hackathons: Starknet CC Hackathon 2022, TPG Hacker House 2022, Aptos Community Hackathon 2023, EthIndia (bounties) 2023, Starknet Hacker House 2023, Aleo ZK hacker house 2023, DLT Climate Hackathon 2024, Solana Colosseum Hackathon 2024, and Unfold Hackathon 2023. GH: “thirumurugan7”

  3. Total Grant Amount
    $52,000; requesting $27,000 for milestone 1.

  4. Milestone 1 Deliverables
    Development of permissionless Winks SDK with Rootstock-specific primitives: Our objective here is to deliver a modular, open-source TypeScript SDK that enables developers to permissionlessly compose and embed Rootstock-native interactions such as token transfers, contract calls, and staking operations within dynamically rendered Twitter-native applications (“Winks”).

    Deliverables:

    Wink SDK core (TypeScript):

    1. Framework-agnostic library with composable utilities and React bindings.

    2. Abstractions for fungible and non-fungible token standards.

    Pre-packaged hooks and wrappers for:

    1. Faucet interactions

    2. Staking contract interfaces

    3. Rootstock RPC call management

    4. Signature request management using EIP-1193-compatible providers

    Wallet integrations:

    1. WalletConnect

    2. RainbowKit

    Callback-oriented interaction layer:

    1. Full support for execution callbacks (success/failure/error).

    2. Message relaying capabilities for social sharing (post-transaction Tweet generation)

    SDK documentation and sample Winks:

    1. Technical documentation hosted via Gitbook

    2. Two examples demonstrating token transfers and faucet drips directly inside Winks

    Technical stack:

    1. Language & runtime: TypeScript + Node.js

    2. Build tooling: Rollup + Vite

    3. Package distribution: NPM & GitHub Packages

    4. Testing framework: Jest + Playwright (for iframe embed testing)

    5. Contracts interface layer: Ethers.js with Rootstock-specific RPC configuration

    Outcomes:

    1. Publish the SDK with complete CI/CD pipelines

    2. Two reference implementations functioning on Twitter’s desktop site (Chrome browser), demonstrating the use of the SDK with Rootstock smart contracts

    3. Developer onboarding via documentation and demo apps optimized for embedding within Twitter/X via Winks

    KPI for this milestone: Milestone 1 should be evaluated based on technical functionality, developer usability, and early signs of ecosystem integration. This milestone is designed to establish the foundational SDK layer required to compose Rootstock interactions within Twitter-native applications (“Winks”). The SDK will expose at least two key Rootstock-native primitives:

    1. Token standards (for transfers and approvals), and

    2. One additional primitive, such as either a faucet interaction or staking contract interface (depending on existing Rootstock tooling availability).

    For developer usability, the SDK will be shipped with a minimum of two functional reference implementations: A Wink enabling a token transfer + A Wink interacting with a testnet faucet or staking contract.

    Each reference implementation will be designed to run in a fixed 1100x1100px iframe and will demonstrate end-to-end functionality, including wallet connection, transaction signing, and success/failure callbacks on Twitter desktop site.

    The SDK will be released as an open-source package via GitHub and NPM, under an MIT license. It will include clear documentation covering installation, usage, example flows, and Rootstock-specific configuration. Documentation will be published via a static documentation generator such as Gitbook.

  5. Milestone 2 & 3
    Requesting $25,000 for milestone 2. *Milestone 2 deliverable: *Backend infrastructure, rendering pipeline, and analytics system for Winks.

    Here, our objective is to develop the backend architecture that powers the lifecycle of Winks: transaction routing, iframe rendering, metadata services, and analytics for measuring campaign engagement inside Twitter. The infrastructure must meet the performance demands of dynamic content delivery within constrained environments such as the Twitter mobile app. Deliverables include a backend API layer:

    1. Transaction Routing: Secure transaction dispatch layer to interface with Rootstock’s JSON-RPC endpoints.

    2. Dynamic iframe renderer: SSR layer that renders React apps at fixed resolution (1100x1100px) optimized for Twitter’s desktop feed.

    3. Metadata service: JSON metadata endpoints for Winks, including title, description, media hash.

    Frontend rendering and optimization:

    1. Framework: Next.js + React

    2. Viewport constraints: Rendering confined to 1100x1100px bounds

    3. Dynamic UI embeds: Enables buttons, animations, and wallet-triggered flows within iframe, without redirecting users out of Twitter

    Analytics layer via Firebase to track impressions, click-throughs, on-chain interactions, bounce rates and view durations while supporting anonymized user segmentation for performance benchmarking.

    Tech stack:

    1. API and rendering: Node.js, Next.js (Edge runtime), React

    2. Cloud infra

    3. Analytics: Firebase

    4. Security: CORS-enforced APIs

    Outcomes:

    1. Live production-ready infrastructure that delivers and tracks Winks on Rootstock.

    2. Load performance benchmarks: <400ms TTFB globally, <1200ms FCP on Twitter desktop

    3. Public dashboard for usage statistics of Rootstock-based Winks

    4. Developer documentation for backend endpoints and analytics events

    To demonstrate early external validation, the team will onboard at least one developer or project from the Rootstock ecosystem to test or experiment with the SDK during the milestone period.

    KPIs for this milestone: Here we focus on delivering the backend systems required to support the lifecycle of Winks within Twitter, from transaction routing to dynamic rendering and user engagement analytics. These systems transform the SDK from a static library into a fully functional distribution framework for Rootstock-powered dapps. At the backend, our API routes signed transactions to Rootstock’s RPC endpoints, supporting standard JSON-RPC methods and providing consistent handling of transaction receipts and errors. This API will also include a metadata endpoint serving previews of Winks for rendering inside the Twitter/X feed. All infrastructure and code will be documented, and a high-level architecture diagram will be included in the final milestone report.

  6. Timeline: Overall Duration: 10 Weeks | Milestone 1: Weeks 1 to 5 | Milestone 2: Weeks 6 to 10

    Milestone 1: SDK development with Rootstock primitives (weeks 1 to 5)

    Week 1:

    1. Finalize SDK architecture and modular structure

    2. Define contract abstraction layer (E/RRC-20, faucet or staking)

    3. Set up monorepo, CI/CD pipelines

    4. Begin wallet integration scaffolding

    Week 2:

    1. Implement and test token abstraction (transfer + approve)

    2. Scaffold EIP-1193-compatible signature/request manager

    3. Begin documentation outline on GitBook

    4. Start working on sample Wink #1 (token transfer)

    Week 3:

    1. Implement 2nd Rootstock primitive (faucet or staking)

    2. Complete wallet integration

    3. Continue development on sample Wink #2 (faucet interaction)

    4. Start testing

    Week 4:

    1. Finalize both sample Winks with 1100x1100 iframe rendering

    2. Implement callback system (success/failure flow inside UI)

    3. Publish SDK to GitHub/NPM (beta release)

    4. Draft usage docs for developers

    Week 5:

    1. Final polishing and internal QA

    2. Invite at least one Rootstock ecosystem dev to commence SDK trial

    3. Refine GitBook documentation based on feedback

    4. Submit milestone with completed code, samples, and docs

    Milestone 2: Backend infra, rendering, and analytics (weeks 6 to 10)

    Week 6:

    1. Set up backend project and edge deployment framework

    2. Design and implement transaction routing API (Rootstock RPC compatibility)

    3. Build metadata endpoint

    Week 7:

    1. Begin SSR rendering layer in Next.js + React (fixed 1100x1100 iframe)

    2. Integrate Wink iframe templates with SDK flows

    3. Start Firebase analytics pipeline setup (events: impression, clicks)

    Week 8:

    1. Complete rendering logic for one Rootstock Wink

    2. Integrate wallet flows and test inside Twitter (desktop/mobile)

    3. Add anonymized event logging + segmentation to Firebase

    4. Finalize role-based access/authentication (Firebase auth)

    Week 9:

    1. Build performance test harness to benchmark TTFB and FCP

    2. Deploy second Rootstock Wink (e.g., staking or faucet claim)

    3. Conduct live testing and usage observation

    4. Start dashboard build

    Week 10:

    1. Final infra hardening and error monitoring

    2. Finalize public dashboard and developer API docs

    3. Package and submit full milestone report: code, infra links, metrics, architecture diagram

    4. Coordinate second external developer onboarding (Rootstock dev/tester)

    Total duration: 10 weeks | Key midpoint deliverable: SDK

    Final Deliverable: Fully live infra + 2 Rootstock Winks + analytics by end of Week 10

  7. Technical Specs: SDK architecture and developer tooling: The Winks SDK will be written in TypeScript, published as an open-source package, and designed to be framework-agnostic with optional React bindings. It will abstract common Rootstock primitives and include utilities for seamless integration with wallet providers and smart contracts.

    Core components:

    Token abstractions:

    1. Support for fungible and non-fungible token standards

    2. Prebuilt methods for `transfer`, `approve`, `balanceOf`

    Primitives:

    1. Faucet interaction wrapper (configurable endpoint + transaction trigger)

    2. Staking contract interface

    Wallet integration: Support for WalletConnect and RainbowKit
    Prebuilt examples of two end-to-end Winks: a. Token transfer Wink, and b. Faucet claims Wink. Both examples will render in 1100x1100px fixed iframe format and function inside the Twitter/X feed (desktop)
    Documentation: Authored in GitBook, covering SDK setup & usage, Rootstock configuration, smart contract integration, wallet flows, and sample Wink deployment examples.
    Tooling & Environment:

    1. Language/runtime: TypeScript (Node.js)

    2. Build system: Rollup + Vite

    3. Contract layer: Ethers.js (configured for Rootstock RPC)

    4. Testing Frameworks: Jest (unit tests), Playwright (iframe + wallet interaction tests)

    5. Distribution: NPM (public), GitHub (MIT License), semantic versioning
      Backend infra and rendering:

    6. Transaction router

    7. Metadata endpoint

    8. SSR rendering pipeline

    9. Built using Next.js + React (SSR)

    10. Outputs 1100x1100px dynamic iframe-ready React apps

    11. Supports static fallback for non-interactive Winks

    12. Constrained to iframe sandbox

    13. Optimized for one-screen use (no redirects)

    14. Interactive UI with buttons, wallet prompts, and confirmation states

    Analytics: To track usage, engagement, and campaign impact, a real-time analytics stack will be deployed with minimal overhead using Firebase Realtime DB, anonymous user/session IDs, and event pipelines triggered from iframe events.

    Security features:

    1. Role-based API access via Firebase Auth

    2. Rate limiting

    3. Signature replay prevention or transaction hash validation

    Testing and validation:

    1. Unit tests for SDK core utilities and contract wrappers

    2. Integration tests for wallet connections, transaction flows, and iframe embeds

    3. Manual E2E testing of live sample Winks inside Twitter desktop Chrome

  8. Value Prop for Rootstock: Winks are iframe-embedded Next.js + React apps rendered natively within Twitter using custom metadata. Each Wink comes fully integrated with wallets (ConnectKit/RainbowKit), Firebase Analytics, and Rootstock tooling. On Rootstock, Winks can power onboarding flows, testnet faucets, staking flows, and even governance engagement, all without users ever leaving Twitter.

    Winks are turnkey B2B SaaS tools, requiring zero technical effort from partners to implement protocols. We offer custom Winks (tailored apps for specific use cases) and Wink Generators (self-serve creation tools). We will also deploy an SDK, allowing developers on Rootstock who prefer a DIY approach to spin up their own Winks in a permissionless manner.

    We help the Rootstock ecosystem to improve user onboarding by making it easier, faster, and more Web2.5-friendly. Our project aims to create Winks for all Rootstock projects. These projects target Crypto Twitter: we offer them the ability to engage that Crypto Twitter audience directly within Twitter. Tweets with Winks will increase conversion by reducing user friction from URL redirections.

    This will help Rootstock, and the products built on it, to onboard new users much faster and easily by making those actions simpler within Twitter. Developer onboarding will also become easier with products like faucets accessible within Twitter. In addition to onboarding, Winks.fun can also help Rootstock with user retention by making protocol-related actions (e.g. staking) simpler on Twitter, and by providing user analytics to help ecosystem projects tailor experiences and marketing more effectively based on predictive modeling of users’ past Twitter + on-chain data.

    Winks.fun can also help the ecosystem to gain greater visibility on Twitter - posts that contain URLs are punished by Twitter algo since those direct traffic outside of Twitter. However, Winks keeps traffic within Twitter for much longer, increasing engagement and visibility to posts containing Winks. Winks help projects to enable Crypto Twitter to perform on-chain actions like swap, mint, burn, stake, bridge, and others within Twitter’s native interface, without needing any middleware. This would result in Rootstock benefiting from faster onboarding, wallet creation/connection, and higher user conversion rates, leading to increased TVL, daily traded volumes, and user wallet counts.

  9. Demo and GitHub repo:

Demo video URL: https://drive.google.com/file/d/1rQf-uD1YJyAf5pJg5SEHG7Hf3CLuPWNa/view?usp=drive_link

Github: https://www.github.com/winksdotfun

3 Likes
2

2522 Winks.fun: Updated proposal for Winks on Rootstock

Following our discussions with the Rootstock team, we’ve updated the proposal to make the integration of Winks with Rootstock a lower-risk proposition with faster time-to-value. Details follow.

Updated grant amount requested: $27,000; requesting $9000 for milestone 1.

Milestone 1 : Core SDK foundation (Weeks 1-2)

Duration: 2 weeks

Funding ask: $9000

Focus: Essential SDK architecture and basic Rootstock integration

Deliverables for milestone 1:

Wink SDK core (TypeScript):

  1. Framework-agnostic library with composable utilities

  2. React bindings for hooks

  3. Rootstock RPC call management

  4. EIP-1193-compatible provider integration

Token standards support:

  1. Abstractions for ERC-20 token transfers

  2. Basic ERC-721/ERC-1155 NFT support

  3. Token approval functionality

Wallet integration:

  1. WalletConnect or RainbowKit integration

  2. Signature request management

Core infrastructure:

  1. TypeScript + Node.js setup

  2. Rollup + Vite build configuration

  3. Jest + Playwright testing framework

KPIs for milestone 1:

  1. SDK can connect to the Rootstock testnet

  2. Token and NFT transfer functionality works

  3. Wallet provider functional

  4. Package builds and can be imported

Milestone 2: Advanced features and first sample Wink (Weeks 3-4)

Duration: 2 weeks

Focus: Staking, interaction layer, and first working implementation

Funding ask: $9000

Deliverables for milestone 2:

Staking contract interfaces:

  1. Pre-packaged hooks for staking operations

  2. Staking contract interaction abstractions

Callback-oriented interaction layer:

  1. Success/failure/error execution callbacks

  2. Message relaying for social sharing

  3. Post-transaction Tweet generation capabilities

First reference Wink:

  1. Token transfer Wink (1100x1100px iframe)

  2. End-to-end functionality with social sharing

  3. Works on Twitter desktop (Chrome)

Faucet integration:

  1. Testnet faucet interaction

  2. Pre-packaged faucet hooks

Documentation starts:

  1. Basic README with installation instructions

  2. API reference for core functions

KPIs for milestone 2:

  1. Staking functionality integrated

  2. One ready Wink with a pre-defined function

  3. Successful transactions with Tweet generation

  4. Faucet and staking operations are working

Milestone 3: Complete implementation and release (Week 5)

Duration: 1 week

Focus: Second implementation, comprehensive documentation, and full release

Funding ask: $9000

Deliverables for milestone 3:

Second reference Wink:

  1. Staking, faucet, or NFT interaction Wink

  2. Demonstrates advanced SDK capabilities

Package distribution:

  1. NPM and Github package publication

  2. Complete CI/CD pipelines

Comprehensive documentation:

  1. Technical documentation via Gitbook

  2. Usage examples and Rootstock-specific configuration

  3. Developer onboarding materials with demo apps

Testing suite:

  1. Playwright iframe embed testing

  2. Complete test coverage

KPIs for milestone 3:

  1. Two working reference implementations (token transfer + faucet, staking or NFT)

  2. Published SDK packages with automated CI/CD

  3. Complete Gitbook documentation live

  4. Testing pipeline functional

Looking forward to the Rootstock community’s support, and to bringing Winks to Rootstock very soon!

2 Likes
3

Thanks for sharing this proposal, it’s an interesting idea.

One thing I’m not fully clear on: from what I’ve read, Twitter/X Player Card policy explicitly forbids interactive experiences inside the feed (things like sign-ins, data entry, or purchasing). Since Winks involve wallet connection and signing transactions, how would this work without running into policy issues?

Also, I’m curious, projects like Farcaster Frames and Lens Open Actions already enable on-chain interactions directly in their feeds. In practice, how would Winks differ from what Frames or Lens are doing?

1 Like
4

Hi Kaf! Thanks for your questions.

Farcaster Frames and Lens Open Actions are both for their own platforms. Winks’ main differentiator is its Twitter-native nature, where the larger audience is. A closer comparable to us is Solana Blinks, and our difference from them is that they need users to have a Phantom wallet installed, with the Solana Actions on X setting enabled from the experimental features section of Phantom. Winks don’t need any middleware or extensions.

Our approach to loading on Twitter is similar to that of Blinks. Winks mirror them by keeping by using links with dynamic previews to simulate in-feed action. Policy forbids interactive HTML in player cards, and the feed must stay linear media only. We comply by being simple links with structured JSON that hand off to wallets or external pages, like Stripe/Shopify links. In the defi context, Winks put actions like mint, stake, or swap behind a link, then handle wallet connect and signing off X. The Tweet itself stays static. To create the feel of in-feed interaction, update og images/videos as state changes, for example, after a stake, the preview updates to show “You staked 1 RBTC” or a growing balance, so X sees link and media, while users experience what feels like an interactive defi Wink, without violating policy.

3 Likes
5

Thank you to all the community members, foundation team, and delegates for all your feedback on the potential to bring Winks to Rootstock. We’re now proceeding to the on-chain voting activity, starting with milestone 1.

2 Likes
6

We find Winks.fun to be a particularly interesting project, especially its potential to enable seamless interaction with Rootstock directly on Twitter. Beyond the initial grant funding, we’d like to understand more about Winks.fun’s long-term sustainability. What is the planned business model or revenue model for Winks.fun? And while the team has clearly outlined its strategy for complying with Twitter current Player Card policy, what are Winks.fun’s contingency plans if Twitter/X’s policy enforcement changes?

3 Likes
7

Thanks for both the questions.

Our revenue model has two facets:

  1. No-code/low-code Wink builder: Just like how you could use SquareSpace or Wix to create websites with drag-and-drop actions, we’re building a Wink developer that enables non-technical folks to deploy Winks for a variety of use-cases. These have a tiered pricing model based on the features selected, as well as a recurring subscription. We’ll experiment with pricing optimizations over time.
  2. Full-fledged Wink development: Here, we work with projects to deploy custom Winks in a manner that doesn’t need any technical lift whatsoever from their side. For this, we charge an upfront creation fee as well as a recurring maintenance fee.

Regarding Twitter, if policy changes to the extent that Winks cannot render within X as intended, they will still be hosted on a backup page as a fully functional, responsive web app, and the links will then redirect to this page. Our long-term plan is to make Winks multi-platform (X, Discord, Farcaster).

8

Thank you for your proposal! We think bringing on-chain actions to Rootstock directly within Twitter is an interesting idea as it addresses a key friction point for user adoption, and the team’s experience is well noted.

Before we can offer our full support, we’d appreciate some clarifications:

  • Beyond the initial build, could you say something on your strategy for user acquisition?

  • Could you please elaborate in more detail on your long-term revenue model, specifically around the no-code builder etc that you mention? What kind of use-cases do you forsee other launching with Winks?

  • Lastly, what was the reason for the significant reduction in the requested grant amount from the initial figure, and how will this impact the project?

Many thanks!

1 Like
9

Thanks for your questions and for your feedback about Winks’ potential to help Rootstock ease user adoption.

Strategy for user acquisition: We want to target Rootstock-native projects (defi, wallets, NFT initiatives) since for them, Winks are a fast, low-effort growth tool. We also plan to leverage adoption from any other ecosystems we deploy in, to bring developers and users into Rootstock Winks, creating an inbound flywheel. Further, since Winks are native on Twitter, they amplify visibility, and we aim to partner with the Rootstock community and any relevant KOLs to seed adoption around key actions like staking, minting, swaps, and faucet use.

Regarding our revenue model with the no-code/low-code Wink Builder, this is going to be a Wix-style tool for creating Winks for swap pairs, NFT mints, prediction pools, event signup flows, node sale whitelists, pre-sale pages, or various other use cases. We’ve previously made a rudimentary example on BNB Chain of how a Wink generator could work for a token swap pair, and you could try it here, just paste the CA of any token and see the magic: https://buymemes.winks.fun/

We reduced the grant ask to better align with Rootstock’s feedback for a leaner, lower-risk approach. The original scope included ecosystem-level tooling like a Wink generator. The updated scope focuses on the SDK foundation, two reference Winks, and documentation; still high utility, but at a lower cost. With this revised scope, the core delivery isn’t compromised; milestones are sharper and faster. Larger tooling stays on our roadmap to be funded through revenue or future ecosystem support. We’ve adapted a lean MVP approach that brings quicker value for Rootstock, with room to expand as adoption grows.

2 Likes
10

Just want to thank everyone for their excellent questions and Wink’s team for all the clarifications.
I particularly liked this approach, as I have found the original value too high/too risky:

I’m satisfied, I’m supporting this proposal.

I believe Twitter/X has an important role in the future of Crypto.
I’m excited. In case the proposal passes, please keep us updated on the development here.

1 Like
11

Hello winksdotfun. Thank you for your proposal. Do you have examples of case studies / implementations from other ecosystems that you can share?

1 Like
12

Thank you for your support! Definitely, will keep informed here once the proposal passes.

13

Absolutely, happy to share below some case examples:

Soneium: https://x.com/soneium/status/1908160684044534234

Starknet: https://x.com/TestWinks/status/1965384784928248204

TEN Protocol: https://x.com/memespin_io/status/1952420457078202433

Happy to provide any additional info you might need! Thanks!

3 Likes
14

Hi everyone! Happy to report that our deliverables for milestone 1 are ready:

NPM Package:

https://www.npmjs.com/package/rootstockwinks

SDK docs:

Looking forward to feedback on this! We’ve also made good headway on milestone 2, and expect to provide deliverables for that milestones too by end of next week.

1 Like
15

Thanks for sharing the npm package and its document. At a quick glance, we couldn’t find anything related to Rootstock contracts or “primitives” as promised in the code or document, but the library name “rootstockwinks”. Also, the repository linked in the npm page https://github.com/winksdotfun/winksdotfun isn’t accessible. Could you clarify what’s being done for Rootstock with the milestone 1 grant?

2 Likes
16

Hi all, based on feedback recieved, we’ve updated the SDK to make it more consumable for devs. Sharing below some updated links:

https://www.npmjs.com/package/rootstockwinks

Demo: https://youtu.be/j2Atg2jcw04

Thank you, and looking forward to your feedback!

2 Likes
17

Thanks for providing much more detailed document, the demo video and the public repository!

Just to nitpick again, the repository linked in the npm package is still a private repo.

Also,

Are you planning to publish the documentation on a Gitbook as well?

2 Likes
18

hi @Tane - thanks for this. I’ve updated the private to public the same day of your comment. And yes, the Gitbook publication is underway - will update here with the relevant URL here shortly.

3 Likes
19

Confirmed the repo link is changed and thanks for the confirmation on the Gitbook!

2 Likes
20

The Gitbook is up! Winks SDK (rootstock) | Winks Docs

2 Likes