LAYER

739 posts

LAYER banner
LAYER

LAYER

@LayerOnEth

Layer is making @WAVS_WAVS_WAVS the event-driven framework for distributed architectures. Ship fast with verifiable offchain compute.

Beigetreten Aralık 2023
262 Folgt4.6K Follower
Angehefteter Tweet
LAYER
LAYER@LayerOnEth·
welcome to WAVS dashboard + wizard operating a node today means stitching together triggers, components, and submissions while managing logs and CLI workflows WAVS dashboard reduces this complexity run nodes, configure services, monitor execution—all in one place
LAYER@LayerOnEth

x.com/i/article/2039…

English
8
6
23
1.9K
LAYER retweetet
Antoni antoni
Antoni antoni@antoni_antoni_·
Agreed @newmichwill , But you still need a decentralized proactive mechanism to speed up contagion control at block time. And not only via a centralized bot keeper dependency.
Michael Egorov@newmichwill

Phew hopefully @aave solves this. But this is the risk non-isolated lending which everyone loves has. Good scaling properties but higher risks -> risk management is the key (Aave was historically very good with it). It is possible to go fully isolated like markets on @CurveFinance, or one can do hybrid (very complex but very possible). But so far the market did not understand what the advantages are. Maybe Aave v4 hub and spoke model is a step towards the semi-isolated safer direction!

English
0
1
1
136
LAYER retweetet
WAVS
WAVS@WAVS_WAVS_WAVS·
a study analyzing 95 software projects found teams on tightly-coupled integration stacks take 14.7 days on average to ship new features vs event-driven teams ship the same features in 6.3 days 2x faster with the same engineers. that's the event-driven architecture advantage
WAVS tweet media
English
1
1
1
115
LAYER
LAYER@LayerOnEth·
oracles, bridges, keeper bots and serverless functions are 4 external dependencies that can halt your app anytime WAVS is an all-in-one event-driven framework, so don't worry & enjoy your friday 😊
English
0
0
0
64
LAYER
LAYER@LayerOnEth·
@cosmos friends we haven’t forgotten about you 👋 WAVS multichain support now includes deeper integration into the cosmos ecosystem aggregator components can submit to Cosmos chains in addition to EVM environments, with improved chain identification for more consistent behavior across networks this makes it easier to build and operate verifiable services across ecosystems ⚛️
LAYER tweet media
English
0
0
1
107
LAYER retweetet
Antoni antoni
Antoni antoni@antoni_antoni_·
Agreed. Risk management is more than just bugs that can be fixed by security audits. It is a reactive system that act at block time if the potential results of a hack is detected (like supply growth or unusual transfert) So basically we can audit as much as we want, but we mostly need to build guardrails for anormal money flows. Banks are already acting like this, not looking for bugs, but looking for suspicions behavior. And we are using @WAVS_WAVS_WAVS to unlock this verifiable and transparent reactivity.
atiselsts.eth@atiselsts_eth

For one, I believe that audits (for code bugs) are one of the things that DeFi does get right. And better audits or formal verification wouldn't have prevented most of the recent exploits: Resolv, Drift > private key compromise + lack to timelock and other circuit breakers Venus Protocol > economic attack, flagged by audits but ignored Aperture Finance, Solv > bugs in unaudited contracts Makina Finance > vault logic compromise, OOS for audits In TradFi, companies are mandated to do thorough risk management by law. In DeFi, we're not. Solution? More social consensus that DeFi needs to learn to take better care of its risks. This already works with code audits - everyone believes that a protocol that doesn't have code reviewed by security experts can't be taken seriously. It also works for L2s because we have @l2beat. Comparably, we don't have nearly as good insight into the admin control levels of major DeFi protocol deployments. Similarly, we know far more about how to exit L2s in times of crisis than how to exit major DeFi protocols if/when their admin decides to do something funky. EF doesn't need to pick and choose some favorite protocols. But it would be nice to recognize that there's a crisis in "low-risk" DeFi and push for a more principled approach, where risk management goes beyond looking for bugs in the code.

English
1
1
2
268
LAYER retweetet
WAVS
WAVS@WAVS_WAVS_WAVS·
chainlink only supports financial data, limiting its apps @0xEN0VA built a hyperstition market on X follower counts @TrustGraphNet pulls github contributions as trust scores @hydromarkets demo uses email authentication via DKIM WAVS' offchain events unlock the offchain world 🌎
English
0
2
2
172
LAYER
LAYER@LayerOnEth·
happy to report WAVS aggregation has moved to a fully decentralized p2p model no single point of coordination, no bottlenecks, no centralized actor holding the system together verification and submission now emerge from the network itself
English
0
1
4
131
LAYER retweetet
Solva (CryptoCrew)
Solva (CryptoCrew)@crypto_crew·
CryptoCrew is now Solva. We’ve aligned our brand with the company behind it - evolving from validator operations into full-stack blockchain infrastructure. Same team. Expanded vision. Built for what’s next.
Solva (CryptoCrew) tweet media
English
11
7
52
3.5K
LAYER
LAYER@LayerOnEth·
WAVS components now support raw sockets and tls, which means services can communicate with systems like IPFS, email, and other low level protocols directly this makes workflows like our partnership with @hydromarkets possible, where a simple offchain action like email can trigger onchain execution flow
English
0
1
2
242
LAYER retweetet
WAVS
WAVS@WAVS_WAVS_WAVS·
80% of Fortune 100 runs on Kafka, it replaced fragmented duct-taped integrations with one event-driven model. crypto is still behind using 3 separate vendors for oracles, bridges, and keeper bots that are slapped on a blockchain WAVS is the Kafka for verifiable applications
WAVS tweet media
English
0
1
2
168
LAYER retweetet
Edge City
Edge City@JoinEdgeCity·
Thou Ārt Research is building the first serious cross-case study of popup cities. 75 interviews, 48 communities. If you were at @EdgeEsmeralda 2025 or Edge Patagonia, your 12 minutes would make both editions focal cases in the study! Link to take part below ↓
Edge City tweet media
English
2
6
27
1.6K
LAYER retweetet
Funding the Commons
Funding the Commons@FundingCommons·
The hardest questions in AI right now are not technical. They are about power, purpose, and who gets a say. This was Funding the Commons SF: Intelligence at the Frontier. We will be back this fall, stay tuned. 💫
English
3
11
53
2.7K
LAYER
LAYER@LayerOnEth·
gm WAVS devs! we simplified the WAVS execution model removing reliance on internal databases it now runs primarily in memory, which means fewer assumptions, fewer inconsistencies, and better performance across distributed systems if you need persistence, you can still write to external systems like IPF have a good day🫡
LAYER tweet media
English
3
1
6
143
LAYER retweetet
GREEN JEFF
GREEN JEFF@jeffthedunker·
call me old fashioned but i still like decentralized finance
English
11
2
52
1.4K
LAYER retweetet
Gitcoin
Gitcoin@gitcoin·
Every contribution to a quadratic funding round is two things at once: capital and signal. The capital funds builders. The signal – who the community believes is doing valuable work, and how broadly that belief is held – shapes what gets legitimized, sustained, and built next. For example: → 412 contributors validated broad support for EIP-1559 in ways coin voting alone couldn't → 11,000 contributors gave @CoinCenter credibility that no single foundation grant could → Early contributors motivated Plasma Group through unfunded research, before they became @Optimism When funding becomes democratic, participation becomes agency. And the signal becomes just as powerful as the capital 💚 Full report from @owocki ↓ gitcoin.co/research/signa…
English
0
2
57
2.4K
LAYER
LAYER@LayerOnEth·
we designed a drag and drop ‘infra legos’ interface 🧩 WAVS wizard 🧙‍♂️ components lock into place visually, making it easier to structure a verifiable service define triggers, operator components, middleware, and submission logic through a visual workflow give it a try→ docs.wavs.xyz/resources/wavs…
LAYER tweet media
English
0
1
4
155
LAYER
LAYER@LayerOnEth·
wallet and network management are built directly into the dashboard operators can securely manage mnemonic-based wallets, track balances across networks, and configure custom EVM and cosmos chains try the WAVS dashboard → docs.wavs.xyz/resources/wavs…
English
0
0
0
48
LAYER
LAYER@LayerOnEth·
the dashboard integrates with AI tooling through MCP server support this enables connections to systems like Claude and OpenAI Codex for assisted component development, faster iteration, and more efficient service configuration
English
1
0
0
78
LAYER
LAYER@LayerOnEth·
introducing the WAVS dashboard a desktop interface designed for running and managing WAVS nodes and verifiable services unify fragmented workflows, improve execution visibility, and reduce the operational complexity required to run production-grade services
LAYER tweet media
English
1
2
4
222

Entdecken

@newmichwill @cosmos @WAVS_WAVS_WAVS @0xEN0VA @TrustGraphNet @hydromarkets @crypto_crew @gitcoin