Skip to content

feat: Update Discord invites and add support notification for logged-in users#946

Open
EightRice wants to merge 10 commits intomasterfrom
feature/replace-ghostnet-with-shadownet
Open

feat: Update Discord invites and add support notification for logged-in users#946
EightRice wants to merge 10 commits intomasterfrom
feature/replace-ghostnet-with-shadownet

Conversation

@EightRice
Copy link
Copy Markdown
Collaborator

Summary

  • Updated all Discord invite links across the app to use auth-aware URLs: authenticated users get one invite code, unauthenticated users get another
  • Added a support notification system that detects repeated app errors (failed API calls, query failures) and shows a one-time "Get support on our Discord" toast to logged-in users
  • Error tracking hooks into react-query's QueryCache/MutationCache globally, plus key service-layer catch blocks and the existing useNotification error variant

Test plan

  • Verify Discord links in Landing, FAQ, and Footer show the correct invite based on wallet connection state
  • Verify the support notification appears once per session after 2+ errors when wallet is connected
  • Verify the notification does not appear for unauthenticated users
  • Verify the notification links to the correct Discord invite
  • Verify CONTRIBUTING.md has the updated Discord link

- Replace Tezos Ghostnet with Shadownet (RPC: rpc.shadownet.teztnets.com)
- Replace Etherlink Testnet with Etherlink Shadownet (chain ID: 127823)
- Update TzKT explorer links to shadownet.tzkt.io
- Update Etherlink explorer to shadownet.explorer.etherlink.com
- Update Firebase collection names for Shadownet
- Add custom chain definition for Etherlink Shadownet in wagmi config
- Update Beacon wallet config with custom network for Shadownet
- Fix useEthersProvider to handle undefined publicClient gracefully
- Update all tests and E2E specs

Note: Hasura indexer needs to be reconfigured to point to Shadownet.
See MIGRATION-GHOSTNET-TO-SHADOWNET.md for full migration checklist.
- Upgrade @airgap/beacon-sdk and @airgap/beacon-types from 4.2.2 to 4.7.0
- Use NetworkType.SHADOWNET instead of NetworkType.CUSTOM
- Remove WalletConnect version pinning that conflicted with newer Beacon SDK
- Simplify wallet creation since Shadownet is now a first-class network type

This fixes Kukai wallet connection issues on Shadownet.
- TxStatus.tsx: Update explorer URL to shadownet.explorer.etherlink.com
- stats/index.ts: Update Etherlink explorer API URL pattern
- web3provider.tsx: Use etherlinkShadownet instead of etherlinkTestnet
…Shadownet

The wallet was connecting to mainnet instead of shadownet because
requestPermissions() was called without a network parameter. This fix
explicitly passes the network config (including rpcUrl for shadownet)
to requestPermissions(), ensuring the wallet connects to the correct network.
…in users

Update all Discord invite links to use auth-aware URLs (authenticated
vs unauthenticated). Add a support notification that shows once per
session when logged-in users experience repeated app errors, directing
them to the Discord for help.
@netlify
Copy link
Copy Markdown

netlify bot commented Mar 16, 2026

Deploy Preview for tezos-homebase ready!

Name Link
🔨 Latest commit 3aad065
🔍 Latest deploy log https://app.netlify.com/projects/tezos-homebase/deploys/69b82d45f528230007f5c27d
😎 Deploy Preview https://deploy-preview-946--tezos-homebase.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 27 (🟢 up 2 from production)
Accessibility: 91 (no change from production)
Best Practices: 83 (no change from production)
SEO: 92 (no change from production)
PWA: 70 (no change from production)
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant