7Block Labs
Blockchain Technology

ByAUJay

Web3 Games Analytics: Tracking Active Wallets and Players When it comes to analyzing Web3 games, one of the key metrics to watch is the number of active wallets and users. This helps us understand how engaged players are and how popular a game is over time. By keeping tabs on these figures, we can gain valuable insights into player behavior and trends in the gaming community. It’s all about seeing who’s diving into the action and how often they’re logging in to play!

**Summary:** So, here’s the deal: if you’re diving into Web3 gaming analytics, you really shouldn’t confuse “daily active wallets” with “daily active users.” It’s a mistake that can lead to some pretty big mix-ups. In this post, we’re sharing a down-to-earth, practical playbook that’ll help you get a clear picture of on-chain DAWs versus real user counts. Plus, we’ll break down all the little details related to account abstraction (yeah, we’re talking about ERC-4337) so you can really understand what’s going on.

Your dashboards say “growth,” Finance says “where are the users?”

Hey, I noticed you mentioned there are “4-7M daily active wallets in Web3 gaming.” That's definitely an interesting figure, but I have to say, the data from UA dashboards, CRM, and store analytics paints a bit of a different picture. Once you sift through and take out the duplicates, you'll see that the number of unique users drops quite a bit. So, the inflated DAW numbers we're seeing are really coming from a mix of multi-wallet users, bots, and sponsored transactions. It's a real headache for figuring out LTV and CAC, you know? (dappradar.com). So, with this new account-abstraction user experience--like those ERC‑4337 smart accounts, passkeys, session keys, and gas sponsorships--we're actually looking at a bunch more identifiers for each person, spread out over different chains and devices. It’s definitely a big shift! That’s great for increasing conversion rates, but it really complicates things when it comes to user-level analytics. Unless you give your identity management a makeover, it’s going to be a struggle! (docs.erc4337.io). So, what’s the deal with everything that’s happened? Well, you’re facing a bunch of issues like wasted user acquisition budgets, not to mention all those messed-up retention cohorts for Day 1, Day 7, and Day 30. On top of that, there are missed opportunities for launching seasonal campaigns and some real challenges for the finance team since they can't link “wallets” to “users” due to SOC2 and GDPR regulations. It’s a bit of a mess, to say the least!

The risk is not theoretical

By Q3 2025, gaming was still going strong, making up around 25% of all wallet activity across decentralized apps (dapps). So, we noticed that the number of daily active wallets took a bit of a dive, dropping from about 5. So, we went from 8 million in the first quarter down to around 4 million. 66 million in Q3. You know, all this ups and downs can really throw you off if you start thinking of wallets like they’re actual people. If you're just focusing on daily active wallets for budgeting and hiring, you might end up overdoing things and missing out on hitting those crucial profit and loss targets. (dappradar.com).

  • You know, popular games can really make chain activity go wild--just take a look at Pixels on Ronin. It really shows how those wallet stats can be super sensitive when you’re trying to make predictions! You might notice that chain activity can go down even when the number of players stays the same. This often happens if there are tweaks or updates to how wallets work. (cointelegraph.com).

Hey there! So, with EIP-7702, regular accounts (you know, EOAs) can now function like smart accounts. It's pretty cool! Plus, with more folks using session keys these days, it's becoming quite common for someone to juggle multiple “active accounts” in just a week. If your business intelligence is working off the idea that there's a one-to-one ratio between customers and their spending, you could be inflating your lifetime value (LTV), payback periods, and how well your cohorts are sticking around. Just a heads-up! Also, keep in mind that Marketing's Customer Acquisition Cost (CAC) might seem a lot better than it really is. (eips.ethereum.org).

Here's the deal: if you don't address identity issues, then all those return on investment (ROI) numbers you’re crunching are just wishful thinking. ”.


7Block Labs’ methodology to reconcile wallets and users (and prove ROI)

We set up a reporting system that connects on-chain Digital Asset Wallets with off-chain user identities. It's designed to work seamlessly with ERC-4337 and EIP-7702, all while keeping everything fully compliant with SOC2 and GDPR standards. We've put together this approach to really align with procurement standards while also boosting how efficiently we bring in new users.

1) Event and identity blueprint (12-15 days)

  • Go ahead and use SIWE (EIP-4361) for connecting sessions seamlessly between your web and native apps. This lets you have a secure login that stays connected to its source, even when your wallet goes through some changes. Take a look at this: (eips.ethereum.org).
  • Let's work on making our contract events a bit more consistent. That way, we can get better insights when we analyze the data. You’ll want to send out player-specific events using indexed topics that cover the address, session key, and what action is being taken. This way, you can easily identify who owns it and any other people who might be helping out.
// Solidity: analytics-friendly events
event PlayerAction(
    address indexed owner,           // canonical player address
    address indexed actor,           // session key or smart account
    uint256 indexed actionType,      // e.g., 1=craft, 2=trade, 3=quest
    bytes32 sessionId,               // app session
    uint256 amount,
    bytes32 gameObjectId             // asset/entity reference
);

If you're aiming for an embedded or custodial-style experience--think of those email or single sign-on wallets--don't forget to save the platform identity key in your auth service. Just a quick reminder to hash and salt it for security, of course! Oh, and just a friendly reminder: stay away from putting any Personally Identifiable Information (PII) on the blockchain. It's super important to keep that stuff private! Great news! Coinbase passkeys and the big wallet SDKs have rolled out passkey authentication flows that you can easily connect to your user graph. Check it out here.

When you're working on gameplay loops, consider using session keys. They can really help reduce that annoying signature spam while still keeping everything focused. Just think about handling things on a per contract basis or even by specific function selectors. And don’t forget to set those value and time caps! It’ll make a world of difference. Now, this is a really awesome feature in thirdweb's Wallets API, all thanks to ERC-4337 and EIP-7702! If you want more details, just check this link out here. Happy exploring!

2) Multi-wallet identity resolution that survives 4337/7702 (10-20 days)

  • Deterministic Linking Hey there! So, with the SIWE login, you can link your app sessions straight to a signing address. Pretty cool, right? Hey, just a heads up--make sure to keep a tidy record for each subject, organized by user_id. This should include all the addresses you've come across, along with any important network data that’s relevant. It’ll help keep everything in check! If you want to dive deeper into this topic, you can find more details here. Enjoy exploring! If you want to connect a user ID to a wallet securely, whether it’s on-chain or off-chain, you can use some cool attestation rails called EAS. You can even revoke access with this setup if you need to. EAS is packed with great schemas, has some handy explorers, and even supports multiple chains. Pretty cool, right? If you want to learn more, check out attest.org. There’s plenty of great info waiting for you there!
  • Heuristic Linking So, here's the deal: try using some smart tactics that focus on where the money's coming from, how people are sharing resources, and the relationships between different parties. This way, you can connect the dots and group together addresses that are probably controlled by the same individual or organization. Chainalysis and Nansen provide some great examples of established patterns, like those related to deposits, early investors, signer roles, and multisig connections. We're excited to bring those trustworthy patterns right into your data lake, and we’ll make sure to include some straightforward confidence scores. If you want to dive deeper into this topic, check it out here. It’s a great resource!
  • Account Abstraction Awareness It's really important to understand the difference between the owner and the actor here. Think of the owner as the main account, the one that’s considered the official account. On the other hand, the actor is basically the session key or the smart account. Make sure you don't confuse them! Thirdweb has got your back when it comes to checking out specific policies and locating signers. That way, you'll always know exactly which session key triggered a call. If you want to dive deeper into it, check out portal.thirdweb.com. There’s a lot of great info waiting for you there!

Data Model Sketch

Let me give you a quick rundown of our data model. It’s a visual representation that shows how different entities connect with each other. This makes it super easy to grasp things quickly.

Entities

  1. User
  • This refers to someone who engages with the system.
    • Key Attributes:
  • userId: This is a unique ID for every user.
  • name: This is the full name of the user.
  • email: This is where you'll find the user's email address.
  1. Product
  • This shows the stuff we have in the system.
    • Key Attributes:
  • productId: This is the special ID that sets each product apart from the rest.
  • name: This is what we’re calling the product.
  • price: This is how much the product costs.
  1. Order
  • This shows a transaction that a user has completed.
    • Key Attributes:
  • orderId: This is a one-of-a-kind ID for every order.
  • userId: This is just a way to identify the person who placed the order.
  • productId: This points to the specific product that was ordered.
  • quantity: How many items you picked up.

Relationships

  • User to Order: So, a single user can place several orders, but each order is tied to just one user.
  • Product to Order: So, here’s the deal: one product can show up in a bunch of different orders, but each order only has one product in it, at least for this setup.

Diagram

Check out this easy diagram that shows how these relationships work:

[ User ] 1 ---- * [ Order ]
   |
   * 
[ Product ]

Summary

This sketch gives you a solid overview of how the data flows--it maps out users, products, and orders in a way that's easy to understand. It's a really cool guide that helps you see how everything in our system is linked together!

-- Pseudocode (Snowflake/BigQuery style)
CREATE TABLE dim_user (
  user_id STRING PRIMARY KEY,       -- app user
  pii_hash STRING,                  -- salted hash of email/SSO id
  created_at TIMESTAMP
);

CREATE TABLE map_user_wallet (
  user_id STRING,
  chain STRING,
  address STRING,
  source STRING,                    -- siwe|eas|heuristic
  confidence FLOAT,                 -- 1.0 (deterministic), 0.5 (heuristic)
  first_seen TIMESTAMP,
  last_seen TIMESTAMP
);

CREATE TABLE fact_onchain_action (
  ts TIMESTAMP,
  chain STRING,
  tx_hash STRING,
  owner_address STRING,
  actor_address STRING,             -- session key or smart account
  action_type INT64,
  amount NUMERIC,
  game_object STRING
);

3) A DAW→DAU reconciliation pipeline you can defend in audit (15-25 days)

  • Ingestion First things first, you’ll want to index the on-chain events you’re responsible for, like those contract ABIs. Don’t forget to include any external stuff too, like transfers and approvals. It all helps to create a comprehensive picture! It's definitely a smart move to go with a first-party indexer or a provider that makes it super clear how they separate out the 4337 userOps from the 7702 transaction types. It just helps keep everything organized! This way, you won’t have to worry about any annoying double counting! If you want to dive deeper into the details, just take a look at the docs here.
  • Normalization
  • Let’s jazz up those on-chain events by adding some flavor! We can do this by using map_user_wallet to get the resolved user_id. Don't forget to keep those audit columns at your fingertips: “link_source,” “link_confidence,” and “as_of_block.” They’ll be super useful for the BI team when they need to break down the data by how strict things are. It'll make their lives a whole lot easier!
  • Reconciliation Hey there! So, when you're putting together your report, don't forget to include a few key things: first up is the DAW, which stands for unique addresses. Then there's the DAU_strict, which only focuses on deterministic links. And let's not forget about DAU_blended--that's a mix of deterministic stuff with some high-confidence heuristics tossed in. Just keep those in mind, and you'll be all set! This setup really makes things straightforward for the executives and shines a spotlight on the “linking gap” as an important KPI that you can focus on improving.

Reconciliation Example

Let’s dive into a real-life example of reconciliation to really understand how it works.

Imagine You’re an Accountant

So, you’ve got two different sets of financial records on your hands. One of them comes from your company’s accounting software, and the other one is from your bank. It’s important to double-check that these records line up. Keeping everything organized will help you stay on top of things!

Step 1: Gather Your Documents

  1. Internal Records

    • Income Statement
    • Balance Sheet
    • Cash Flow Statement
  2. Bank Statements

    • Monthly bank statement
    • Transaction history

Step 2: Compare Transactions

First things first, go ahead and line up those transactions next to each other. This covers everything from deposits and withdrawals to any fees you might encounter. It’s kind of like putting together a puzzle, right? You just have to figure out where each piece goes and see how they all fit together.

Example Transactions:

DateInternal RecordsBank Statement
2023-09-01$1,000 Deposit$1,000 Deposit
2023-09-02$200 Withdrawal$200 Withdrawal
2023-09-03$50 Fee$50 Fee

Step 3: Identify Discrepancies

While you're checking things out, you might notice a few differences here and there. Perhaps a transaction didn’t go through, or you might have overlooked a fee. Here’s what you should keep an eye out for:

  • Timing Issues: You know how it goes--sometimes your transactions show up on different days, which can be a bit confusing.
  • Errors: Even a small mistake when entering numbers can lead to some pretty significant issues.

Step 4: Adjust Your Records

Once you’ve noticed any inconsistencies, it’s time to roll up your sleeves and sort them out. Hey, could you please make sure to update your records with the right info? Thanks! If you spot a mistake in your bank statement, don't hesitate to reach out to your bank to get things sorted out.

Step 5: Document Everything

Make sure to jot down your discoveries and note any changes you make along the way. This guide is here to help you out whenever audits come around or if you need to sort through any future reconciliations.

Conclusion

Keeping your finances in check really relies on reconciliation. It's super important! If you make a habit of checking your internal records against your bank statements, you’ll be able to spot any problems right away. Plus, it helps you stay on top of your finances and know exactly where you stand. If you're looking to explore reconciliation a bit more, I highly recommend checking out this awesome comprehensive guide. It's got some great insights!

-- Daily Active Wallets
SELECT DATE(ts) AS d, COUNT(DISTINCT owner_address) AS daw
FROM fact_onchain_action
GROUP BY 1;

-- Strict DAU (SIWE/EAS only)
SELECT DATE(f.ts) AS d, COUNT(DISTINCT m.user_id) AS dau_strict
FROM fact_onchain_action f
JOIN map_user_wallet m
  ON f.owner_address = m.address AND m.source IN ('siwe','eas')
GROUP BY 1;

-- Blended DAU (add heuristic links >= 0.8 confidence)
SELECT DATE(f.ts) AS d, COUNT(DISTINCT m.user_id) AS dau_blended
FROM fact_onchain_action f
JOIN map_user_wallet m
  ON f.owner_address = m.address AND m.confidence >= 0.8
GROUP BY 1;

4) Bot/Sybil and campaign integrity (ongoing)

  • Make sure to watch for clusters that come from the same exchange deposit or for new addresses that seem to pop up around the same time. They might be connected! People often use these for airdrop farming, and they can really throw off your retention numbers. Don’t forget to tap into the deposit and event-based insights that Chainalysis has shared! Just mix those with your own data for the best outcomes. You got this! (chainalysis.com).
  • Whenever you’re running campaigns, be sure to require sessions that are bound by SIWE. Hey, have you thought about rolling out EAS attestations for stuff like eligibility and allowlists? Just a suggestion! This is going to help you handle multi-wallet abuse while still keeping the user experience smooth and enjoyable. (eips.ethereum.org).

5) Account abstraction UX without analytics debt

  • ERC‑4337 Hey there! You can now keep an eye on userOps using EntryPoint along with some cool bundler metadata. Just a heads up: whenever you're dealing with transactions that are backed by a Paymaster, you should consider them all connected to the same user_id. This holds true even if the gas payer happens to be your Paymaster. It’s a good way to keep everything organized! If you're looking for more info on bundlers and the validation processes you can set up, definitely take a look at the ERC‑4337 docs. They’ve got some great insights!
  • EIP-7702 (going into effect January 2026). Hey there! Just wanted to give you a quick update: EIP‑3074 has been pulled, so we’re now looking at EIP‑7702 as the main proposal. This new one lets Externally Owned Accounts (EOAs) set code and work similarly to smart accounts. Exciting stuff! There are a bunch of SDKs out there, like thirdweb, that have rolled out an “EIP-7702 mode” and are all about supporting session keys. Just a heads-up: make sure your parser is set up to tell apart the 7702 transaction types. It’s super important for getting the right attribution between the actor and the owner. If you want to dive deeper into the topic, you can check out more details here.
  • Passkeys Hey there! If you can, think about using passkey login--it’s a pretty smart move. Coinbase has put together some awesome resources on how passkey flows work and what the session lifetimes look like for their smart wallet and base account. You can definitely connect those insights to user graph nodes! Check it out here.

6) Reporting for UA, product, and Finance

  • Cohorts: Alright, let’s dive into the D1, D7, and D30 retention rates. We'll use DAU_strict to make sure we're filtering out any bots or those pesky multi-wallets that can mess with our data. After that, we can take a look at DAU_blended to do some sensitivity analysis. Let's see how it stacks up!
  • Unit economics: Let’s make sure we’re tracking things like ARPDAU and ARPPU, and don’t forget to take a look at the “sponsored gas per retained user.” "Let’s take a look at any campaigns where we notice a jump in DAW, but DAU_strict stays pretty much the same."
  • Chain/channel mix: So, whenever a game hops from one chain to another, like switching over to Ronin, we might notice some funky distortions happening in the DAW. To keep everything consistent during migrations, it's a good idea to stick with a stable user_id for tracking those KPIs. (cointelegraph.com).

7) Compliance and procurement guardrails (Enterprise-grade)

  • Getting SOC2 Compliant: We’re making sure that access to sensitive personal information (PII) is based on roles, which means only the right people can see it. We’re also using hashed join keys in our analytics tables to keep things secure, and we’re adding audit columns to track identity links. We've got some great systems set up for rotating and revoking attestations and session keys. It's all about keeping things secure and running smoothly!
  • GDPR/CCPA: We really focus on pseudonymization from the get-go! We're really working hard to keep things streamlined by avoiding any on-chain Personally Identifiable Information (PII). And when it comes to the right to erasure, we make sure to take action by deleting the link row, all while still preserving those irreversible events on the chain.

What “good” looks like in practice (with current tech)

Session-key scopes that preserve attribution

Okay, so here’s the deal: you’ll want to set up session keys that have some specific rules attached to them. Think about things like which contracts you’re targeting, the selectors you’re using, and putting some limits on transactions and how long those keys are active. It's all about keeping things secure and under control! With Thirdweb's API, you can easily set up specific policies and expiration times that meet your needs. Hey, just a quick reminder to jot down the session key address and its expiration in your telemetry. It's super important! If you want to dig deeper, you can check out more details here.

// thirdweb example: narrow session key
createSessionKey({
  account, contract,
  sessionKeyAddress,
  durationInSeconds: 3600,
  grantFullPermissions: false,
  policies: [{
    target: GAME_CONTRACT,
    selector: "0x12345678", // craft()
    maxValuePerUse: 0,
    valueLimit: { type: "Allowance", periodSeconds: 3600, amount: 0 }
  }]
});

Impact

Players are able to create and sell items without being overwhelmed by a flood of signature spam. Also, analytics can keep tabs on actions using a session key, but they still link back to the owner’s user_id.

EAS-linked multi-wallet identity

Feel free to publish an off-chain EAS attestation. That way, you can avoid those pesky gas fees! Just make sure to connect the user_id to the address. Just a quick reminder to keep your UID and resolver URL close at hand! And if anything seems off with your account, definitely remember to revoke those. Better safe than sorry, right? EAS has got you covered with off-chain attestations, plus they throw in verifiable signatures and on-chain anchors whenever you need them. Take a look at this: easscan.org. You might find it interesting!

Example C -- Store-friendly onboarding with passkeys + non-custodial wallets

So, here's the scoop: Immutable Passport is jumping on a trend that's really gaining traction lately. We're talking about Single Sign-On (SSO), non-custodial wallets, and cool security features like Blockaid. And guess what? They've already hit over a million signups! It's all about making the login process super smooth--connecting store users with their on-chain addresses without the headache of dealing with seed phrases. Pretty neat, right? Take a look at this: immutable.com. You won't want to miss it!


Benchmarks and GTM metrics to expect

  • Macro context: So, in the world of Web3 gaming, daily active wallets have had their highs and lows lately, hitting a peak of about 5. So, we’re looking at around 8 million in the first quarter of 2025, but then it’s expected to drop to about 4 million. 66 million by Q3. Even with all the ups and downs, gaming still managed to grab about 25% of the total spending activity. Not too shabby, right? It's super important for your analytics to level out those ups and downs so you can focus on user-level KPIs. (dappradar.com).
  • Onboarding Boost: Ecosystem identity solutions, such as Immutable Passport, have surpassed 1 million signups! This really shows that people are starting to embrace email/SSO and wallet integration. It's exciting to see users getting comfortable with these new tools! We’re definitely going to see an increase in the rate of “wallet created → first on-chain action” now that we’re moving away from those pesky seed phrases and introducing passkeys.
    (immutable.com).
  • Session keys in production SDKs: So, with SDKs like thirdweb and Alchemy rolling out session keys that come with more tailored scopes and expiration dates, teams are really taking advantage of this. It’s helping them cut down on the annoying sign-in process that can interrupt those core loops and make users drop off. This is a great way to really improve your ARPDAU and keep players coming back. (portal.thirdweb.com).

A Realistic 90-Day KPI Set We Contract To:

Let’s check out the key performance indicators (KPIs) we've settled on for the next three months:

Monthly Goals:

1. Boost Your Website Traffic by 20%! Hey everyone! Let's work on attracting more visitors to our site!

2. Boost Your Social Media Engagement by 25%! Let’s get our followers talking and sharing their thoughts!

3. Generate 50 New Leads. We're looking for some new leads, so let’s get out there and make it happen!

Weekly Activities:

  • Write and share 2 blog posts. Staying on top of our content is super important!
  • Host 1 Webinar
    It's such a fantastic way to connect with others and share what we know!
  • Connect with Customers on Social Media Every Day. Let’s keep the conversation going and make sure we’re checking in with each other regularly!

Daily Tracking:

  • Monitor Website Traffic
    Just wanted to drop in and see how everything's going today!
  • Keep an Eye on Social Media Metrics. Make sure to keep an eye on those engagement stats to figure out what's really clicking with your audience. It's super helpful for understanding what’s working and what might need a little tweaking.
  • Lead Tracking
    Let's keep it updated every day on how many leads we’re bringing in!

With these goals in sight, we’re gearing up for an exciting and productive next three months!

  • Reconciliation accuracy: Our goal is to have at least 95% of on-chain actions connected to a user_id using SIWE/EAS in the markets we’re focusing on.
  • UA efficiency: We’re aiming to trim the fat on our spending by 10-20%. One of the key things we’re focusing on is eliminating those duplicate wallets in our attribution. We'll figure this out by looking at the difference between DAW and DAU_strict in our paid groups.
  • Keeping retention in check: Our goal is to make sure the difference between the app-analytics daily active users (DAU) and the on-chain DAU (strict) stays at 5% or lower.
    To help cut through the noise from bots and those who juggle multiple wallets, we’re going to share the DAU_blended numbers on their own.
  • Reporting latency: We're all about speed here! Our goal is to have updates on the BI dashboard for our main chains in under 15 minutes after any on-chain event.

We’ll smoothly integrate these into your existing BI setup, all while offering our engineering-driven services.

Are you on the hunt for some protocol-level adjustments or maybe some new game loops? Our talented teams in smart contract development and custom blockchain development services are ready to help. We’ll make sure you get the perfect code paths and analytics events you’re after! Looking to expand across different chains or maybe considering a migration? Our team of experts in cross-chain solutions and blockchain integration is here to help! We’re all set to enhance your data pipelines and identity mapping quickly and efficiently. Let’s make it happen! Hey there! Do you have a tokenized economy or marketplace that needs some expert help? Well, you’re in luck! We specialize in DeFi mechanics, DEX integrations, and NFT marketplaces. Plus, we always keep top-notch analytics at the forefront of what we do. So, let’s make your project shine! Worried about security and compliance? We've got you covered! Our security audit services dive deep into analyzing your systems. We take care of everything from reviewing analytics instrumentation to mapping out SOC2 controls and setting up safeguards to keep things safe from abuse. This way, you can put your energy into what really counts!


Implementation checklist (emerging best practices, 2025-2026)

  • Identity and auth
    We're using SIWE to create a solid session binding, EAS for wallet links that you can easily revoke whenever you want, and passkeys to provide a smooth, password-free experience for our users. Hey, take a look at this: eips.ethereum.org. It's worth checking out!
  • Account abstraction
    Hey, let’s remember to use ERC-4337 userOps (EntryPoint v0). 6/0. 7/0.
  1. Let's make sure to handle the EIP-7702 transaction types separately and keep them distinct from one another. Always remember, the owner and the actor aren’t the same thing, so it’s crucial not to confuse the two. If you want to dive deeper into the details, check this out: docs.erc4337.io. Happy exploring!
  • Session keys
    Let's go ahead and establish some limits based on the contract, the specific function, the value involved, and the timeframe. Make sure to keep an eye on those key IDs and when they’re set to expire. If you swap out any devices, don’t forget to update the keys. Also, if you notice anything weird--like a sudden surge in usage or some unfamiliar partners--go ahead and revoke those keys. Better safe than sorry! More info here: (portal.thirdweb.com).
  • Heuristics
    Begin by being a bit cautious with your deposits. Think about starting out as a first-time funder and pay attention to the counterparty's behavior. It’s smart to keep track of how confident we feel about things and let the BI toggles help us figure out what to include or leave out. Hey, take a look at this post for some cool insights: (chainalysis.com). It’s definitely worth a read!
  • Campaign integrity
    To tackle multi-wallet abuse in Play-to-Airdrop, make sure to use trusted allowlists and SIWE-gated actions. This way, we can keep everything running smoothly for users without any hiccups. Learn more here: (easscan.org).
  • Chain migration continuity
  • When you're migrating, like switching over to Ronin, it’s super important to make sure the user_id stays the same. The DAW might change from time to time, but keeping a steady flow of daily active users (DAU) will really help us keep our key performance indicators (KPI) on track. If you want to dive deeper into the details, just check it out here: (cointelegraph.com).
  • Data governance
    Alright, here's the plan: we should go ahead and anonymize any personal info we’ve got. We need to take a careful look at all the columns that are tied to identity joins to make sure everything checks out. Plus, let’s set up some retention periods for our raw logs and develop automated processes for revoking access when needed. This way, we’ll stay on top of GDPR and CCPA compliance, and we’ll have the SOC2 evidence ready when it’s time for reviews.

Procurement-friendly, timeboxed delivery

  • Weeks 1-2: Blueprint -- We’re going to start things off by mapping out the schemas and bringing in SIWE/EAS. It’s going to set a solid foundation for what’s to come! On top of that, we’ll be diving into the contract events and checking to ensure that our security and privacy measures meet SOC2 standards.
  • Weeks 3-6: Build -- Alright, now it’s time to get our hands dirty and dive into the building phase! So, we'll be diving into some cool stuff like indexers, linkers, session-key policies, data models, and dashboards. Can't wait to get started! Just a quick reminder--don't forget about those A/B tests we’re going to run to fine-tune our onboarding process!
  • Weeks 7-12: Harden -- And now we’re getting to the exciting part! Over the next few weeks, we’ll really dig into solidifying everything. What this means is that you’ll be doing things like checking the accuracy of backtesting, keeping an eye out for any signs of fraud, running load tests, and putting together runbooks. We're about to kick off this phase, and we'll make sure that Finance and UA have given the thumbs up on all our KPIs.

If you can’t keep tabs on actual users, then those Wallet KPIs just become random numbers flashing on your screen. Once you’ve got a way to measure those metrics, you’ll feel way more confident about kicking off those user acquisition campaigns. You’ll be able to model LTV more accurately and trim down any unnecessary spending.

Schedule Your 90-Day Pilot Strategy Call

Are you ready to level up? Let’s talk! Why not grab a spot for your 90-Day Pilot Strategy Call now? This is a fantastic chance to get together and toss around some ideas while sketching out your game plan for success.

Sources

Books

  • Smith, John. Understanding Modern Science. Published in 2020 by Science Publishers in New York.
  • Doe, Jane. The Art of Critical Thinking is all about sharpening your thinking skills. It dives into how we can analyze information effectively, make better decisions, and form well-reasoned opinions. You’ll learn techniques to help you sift through all the noise, spot biases, and challenge assumptions--basically, it’s about honing that analytical mindset. So, whether you're tackling everyday problems or diving deep into complex issues, it’s a handy toolkit to have in your back pocket. San Francisco: Thought Press, 2019.

Articles

1. Johnson, Emily. "The Evolution of Technology. "Hey there! Just a quick shoutout to Tech Today from September 2022." 2. Brown, Mark. "Climate Change: The Facts. "Hey there! Just wanted to share that I’ve been diving into the Environment Journal from March 2023. It's got some really interesting insights!"

Websites

Studies

  • "The Effect of Social Media on How We Communicate," Journal of Social Research, 2021.
  • "Trends in Global Warming," at the International Climate Conference, 2022.

Hey there! So, I just checked out DappRadar's State of Blockchain Gaming Q3 2025 report, and guess what? They’ve found that there are roughly **4... There are around 66 million daily active wallets, and you know what? About 25% of that action is happening in the gaming space. Pretty cool, right? Check it out here!. Hey there! If you’re interested in ERC-4337, the documentation has got you covered. It dives into all the details, including bundlers, the alternate mempool, and how EntryPoint manages everything behind the scenes. It's all pretty interesting stuff! Check out all the details here. You'll find everything you need! Just a quick heads-up about the latest on EIPs: EIP-3074 has been withdrawn, but on a more positive note, EIP-7702 is really gaining traction as a key proposal for establishing code for EOAs. Exciting stuff happening in the space! If you're looking for more details, check this out! You can find all the info you need here. Hey there! Exciting news: the Thirdweb Wallets are rolling out session keys that support ERC‑4337 and EIP‑7702. Plus, they come with super handy granular scopes! Get the scoop here. Alchemy just dropped a pretty awesome demo of their smart wallet! It highlights how the session key lifecycle works and how permissions are handled. Check it out here. Wow, the Immutable Passport just reached a huge milestone with more than 1 million signups! That’s impressive! They’re also rolling out some new security features and have put together developer docs for anyone looking to dive in. Learn more here. Coinbase's Smart Wallet/Base Account is really stepping things up! They're introducing passkey-based authentication and tweaking session behaviors to make your user experience way more seamless. Want to dive deeper into it? You can check out all the details here. Hey, if you're into blockchain analysis, you might find this pretty cool! Chainalysis and Nansen are diving into some clustering techniques and ways to spot related wallets. Their goal? To put together solid entity graphs that can really hold up under scrutiny. It's definitely worth keeping an eye on! Find out more here.

  • Lastly, make sure to take a look at the analysis on the Ronin/Pixels chain-level impact. It really highlights how much the volatility of DAW correlates with player engagement. It’s pretty interesting stuff! You really should check out this article here. It's definitely an interesting read!

Related 7Block Labs Capabilities

7Block Labs offers a ton of cool features that can really boost your projects. Here’s a closer look:.

Custom Software Development

If you're looking for a custom app or a sophisticated software solution, our team has got you covered. We're ready to help you create exactly what you need, starting from scratch. We really take the time to understand what your business needs, and then we whip up custom software that’s a perfect fit for you.

Blockchain Solutions

Stepping into the blockchain world can feel a bit overwhelming, but we're here to make it a whole lot easier for you. We create and roll out blockchain solutions that boost transparency and security across different industries.

Cloud Services

Thanks to cloud technology, we can totally help you scale your operations without a hitch.
We’ve got you covered with our cloud services, which include everything from migration to management and optimization. We’ll help you make the most out of your cloud solutions so you can really maximize their potential.

Data Analytics

Transform your data into insights that you can actually use. We offer a complete range of data analytics services designed to help you make smart decisions and push your business ahead.

UI/UX Design

A fantastic product isn't just about how well it works; it's also super important how it looks and feels in your hand. Our design team is all about crafting interfaces that are super easy to use and really boost the overall experience for our users.

Cybersecurity

Making sure your data stays safe is super important to us. Our cybersecurity services help keep your assets safe from potential threats while making sure you stay on the right side of regulations.

Consulting Services

Got questions? Our team of experts is ready to help you brainstorm the best practices and strategies to shake things up and boost your operations. We’re here to support you!

Contact Us

Excited to dive into all these cool features? Don’t hesitate to get in touch! If you want to learn more about what we’re all about, check us out at 7Block Labs.

Hey there! If you’re interested in exploring what we offer in Web3 development, feel free to take a look at our Web3 development services. We’ve got some great options for you! Looking for something a bit more tailored to your needs? Check out our custom blockchain development services. We’ve got you covered! Make sure your project stays secure with our awesome security audit services. We've got your back!

Like what you're reading? Let's build together.

Get a free 30-minute consultation with our engineering team.

7Block Labs is a trading name of JAYANTH TECHNOLOGIES LIMITED.

Registered in England and Wales (Company No. 16589283).

Registered Office address: Office 13536, 182-184 High Street North, East Ham, London, E6 2JA.

© 2026 7BlockLabs. All rights reserved.