DeveloperDefi/traverse-protocol

Visit GitHub

Solidity

1 contributors

website

FeaturedAdvertise to 180K+ monthly visitors

Bifrost

Fastest Enterprise AI Gateway for Routing, Governing, and Securing all your AI Traffic

Momentum

How fast DeveloperDefi/traverse-protocol is gaining stars, and where it lands on Trendshift and GitHub Trending

Activity and trending

Stars, forks and merged pull requests each day or month, lined up with the repository's rank on Trendshift Trending

Oct 28 – Nov 5, 2026

Stars +0 in 9 days

Forks +0 in 9 days

Merged PRs 0 in 9 days

Trendshift Trendingwhere the repository ranked each day it made the top 25

Top 25 overall

Oct 28Oct 30Nov 1Nov 3Nov 5

Stars, forks, merged pull requests and Trendshift Trending rank, by day
Day	Stars gained	Forks gained	All languages
Wed, Oct 28, 2026	+0	+0	#21
Thu, Oct 29, 2026	+0	+0	Not trending
Fri, Oct 30, 2026	+0	+0	Not trending
Sat, Oct 31, 2026	+0	+0	Not trending
Sun, Nov 1, 2026	+0	+0	Not trending
Mon, Nov 2, 2026	+0	+0	Not trending
Tue, Nov 3, 2026	+0	+0	Not trending
Wed, Nov 4, 2026	+0	+0	Not trending
Thu, Nov 5, 2026	+0	+0	Not trending
Total	+0	+0

#1 on the list
Rank that day
Not trending

Mentions and achievements

Where people are talking about DeveloperDefi/traverse-protocol, and every badge it has earned

Nov 51 post
- Moving assets across chains often means juggling several apps and steps. Traverse is built to collapse that into one signed intent: what you give, what you want, on which chain, your minimum and a…
  Read full on X, posted by @TRVProtocol
  @TRVProtocol · x.com
Nov 41 post
- Build status, plainly: the Traverse contracts are Solidity on OpenZeppelin 5.x and open source. They are not audited yet, and the public testnet on Base Sepolia is still in progress, not live. Follow…
  Read full on X, posted by @TRVProtocol
  @TRVProtocol · x.com
Nov 32 posts
- Why Traverse intents use EIP-712: your wallet can show each term in readable form before you sign. You see the input, the output, your minimum, the destination chain and the deadline instead of a…
  Read full on X, posted by @TRVProtocol
  @TRVProtocol · x.com
- Why a Dutch auction? The fee offered to solvers rises step by step until one accepts your intent. The first to take it is the one who can fill it most efficiently, and never below the minimum you…
  Read full on X, posted by @TRVProtocol
  @TRVProtocol · x.com
Nov 21 post2 posts
- Anatomy of a Traverse intent: what you send, what you want back, the minimum you'll accept, the destination chain and a deadline. You sign all five once as EIP-712 data, then solvers compete in a…
  Read full on X, posted by @TRVProtocol
  @TRVProtocol · x.com
- Solvers are whoever executes your Traverse intent. They can't change your terms: the minimum and deadline you signed are fixed, and they race each other in a Dutch auction to fill within them. Code…
  Read full on X, posted by @TRVProtocol
  @TRVProtocol · x.com
Nov 11 post
- Sunday build check: the Traverse contracts are open source Solidity on OpenZeppelin 5.x and not audited yet. Public testnet deployment on Base Sepolia is in progress. Read the code and tell us what's…
  Read full on X, posted by @TRVProtocol
  @TRVProtocol · x.com
Oct 311 post
- With a Traverse intent you don't pick the bridge or the route. Solvers compete for the fill in a Dutch auction, and the terms you signed set the floor: if no solver can meet your minimum before the…
  Read full on X, posted by @TRVProtocol
  @TRVProtocol · x.com
Oct 301 post
- A single quote from a single route is one take on the price. A Traverse intent is open to many solvers at once: the terms shift over time and the first solver willing to fill wins, never below the…
  Read full on X, posted by @TRVProtocol
  @TRVProtocol · x.com
Oct 291 post
- Traverse intents are signed as EIP-712 typed data, so your wallet can show readable fields before you sign: what you send, what you get, your minimum, the destination chain and the deadline. Open…
  Read full on X, posted by @TRVProtocol
  @TRVProtocol · x.com