Would you agree to use the devfee to pay for Gemma Tipping Bot fee on Discord? ($100)
Final Results
82%
Yes, use the dev fee.
12%
No, do crowdfunding.
6%
No, different opinion
β€1
π¨ Xeggex Address Officially Blocked (SPORK_21 Activated)
Xeggex hot wallet address has now been successfully blocked on-chain using SPORK_21. This action was completed after the last update, and all outgoing transactions from the following address are now frozen:
Blocked Address:
Technical Details:
You can verify the current network status using the command:
Youβll see the new entry:
All outgoing transactions from this address are now blocked.
* This was accomplished via the on-chain SPORK_21 mechanism and enforced by all upgraded nodes.**
What does this mean for the community?
* The Xeggex address can no longer send or move funds.
* This protects the PEPEPOW ecosystem from potential malicious dumping or further losses.
* The action is transparent, verifiable, and was performed with community and developer consensus.
Thank you for your continued participation and support as we work together to protect the project and move forward! ππΈ
Xeggex hot wallet address has now been successfully blocked on-chain using SPORK_21. This action was completed after the last update, and all outgoing transactions from the following address are now frozen:
Blocked Address:
PTrSnpbVzbKo1M6Z3fN83FXYkiA3tgRQU9Technical Details:
You can verify the current network status using the command:
./PEPEPOW-cli spork show
Youβll see the new entry:
"SPORK_21_FREEZE_BLACKLIST": "blacklist:PTrSnpbVzbKo1M6Z3fN83FXYkiA3tgRQU9;start:1753209508;expires:1753209568"
All outgoing transactions from this address are now blocked.
* This was accomplished via the on-chain SPORK_21 mechanism and enforced by all upgraded nodes.**
What does this mean for the community?
* The Xeggex address can no longer send or move funds.
* This protects the PEPEPOW ecosystem from potential malicious dumping or further losses.
* The action is transparent, verifiable, and was performed with community and developer consensus.
Thank you for your continued participation and support as we work together to protect the project and move forward! ππΈ
π4
π₯³ Weβve reached 600 Discord members! To celebrate this milestone, a massive PEPEPOW airdrop is live now in our airdrop channel. Donβt miss your chanceβjoin and claim!
https://discord.com/channels/1206789719825055754/1395447464135360512
https://discord.com/channels/1206789719825055754/1395447464135360512
π₯2β€1
[VOTE] Proposal: Switch PoW to HooHash V110
Foztor has spoken with Tonto (owner of HTN & HooHash). If PEPEPOW adopts HooHash V110, we would gain:
CUDA miner (NVIDIA)
OpenCL miner (AMD/Intel, to be extended by Tonto)
CPU miner (already available)
This would finally bring full GPU mining support while keeping CPUs competitive.
Pros
- High energy efficiency β lower wattage on both GPUs and CPUs
- CPU remains competitive (not fully displaced by GPUs)
- Resistant to ASIC/FPGA by design
- Attracts more miners β GPU miners can join easily
Cons
- Not a mature PoW β shorter history, less proven than older algos
- Consensus change required β risk in switching to a new algorithm
- Public miner support uncertain β may lose support from existing devs -(e.g., SRBMiner may not adopt HooHash)
Vote Question
Should PEPEPOW switch its Proof of Work algorithm from XelisV2-pepew to HooHash V110?
Options
Yes β Switch to HooHash V110
No β Stay on XelisV2-pepew
Abstain
Voting Period: Aug 21 β Sep 4, 2025
FAQ
Q1: Will I lose my coins or need to swap?
β No. This is only a PoW change. Balances and masternodes remain the same.
Q2: Do masternodes change?
β No economic change. Just upgrade binaries to stay on consensus.
Q3: What about exchanges?
β Exchanges will need a short maintenance window, we will coordinate.
Q4: Can I still mine with the old XelisV2 miner?
β After activation, XelisV2 blocks will be invalid. Please switch to HooHash miners (CPU, CUDA, OpenCL).
Foztor has spoken with Tonto (owner of HTN & HooHash). If PEPEPOW adopts HooHash V110, we would gain:
CUDA miner (NVIDIA)
OpenCL miner (AMD/Intel, to be extended by Tonto)
CPU miner (already available)
This would finally bring full GPU mining support while keeping CPUs competitive.
Pros
- High energy efficiency β lower wattage on both GPUs and CPUs
- CPU remains competitive (not fully displaced by GPUs)
- Resistant to ASIC/FPGA by design
- Attracts more miners β GPU miners can join easily
Cons
- Not a mature PoW β shorter history, less proven than older algos
- Consensus change required β risk in switching to a new algorithm
- Public miner support uncertain β may lose support from existing devs -(e.g., SRBMiner may not adopt HooHash)
Vote Question
Should PEPEPOW switch its Proof of Work algorithm from XelisV2-pepew to HooHash V110?
Options
Yes β Switch to HooHash V110
No β Stay on XelisV2-pepew
Abstain
Voting Period: Aug 21 β Sep 4, 2025
FAQ
Q1: Will I lose my coins or need to swap?
β No. This is only a PoW change. Balances and masternodes remain the same.
Q2: Do masternodes change?
β No economic change. Just upgrade binaries to stay on consensus.
Q3: What about exchanges?
β Exchanges will need a short maintenance window, we will coordinate.
Q4: Can I still mine with the old XelisV2 miner?
β After activation, XelisV2 blocks will be invalid. Please switch to HooHash miners (CPU, CUDA, OpenCL).
Should PEPEPOW switch its Proof of Work algorithm from XelisV2-pepew to HooHash V110?
Final Results
55%
β
Yes β Switch to HooHash V110
39%
β No β Stay on XelisV2-pepew
5%
π€ Abstain
PoW Algorithm Vote Results
The community vote on whether to switch PEPEPOWβs Proof of Work algorithm from XelisV2-pepew to HooHash V110 has now concluded.
Voting Results (2025/8/21 β 2025/9/4)
Discord: 50% Yes / 44% No / 6% Abstain (36 votes)
Twitter: 75% Yes / 0% No / 25% Abstain (4 votes)
Telegram: 55% Yes / 39% No / 5% Abstain (38 votes)
While βYesβ technically reached the 50% mark, the results are very close and opinions remain divided. This makes it difficult to claim a clear community consensus.
Next Steps
We will not proceed immediately with the change. Instead, the DAO will continue discussions and share clearer explanations of the pros and cons for everyone, especially focusing on the core question: Should PEPEPOW remain CPU-only, or move to a low-energy PoW that supports both GPU and CPU mining at near parity?
After this period of discussion, we will hold a second, more focused vote to confirm whether the community truly supports a change.
Why This Matters
Staying on XelisV2-pepew β CPU-only mining, simpler, keeps things as they are.
Switching to HooHash V110 β Enables GPU mining + keeps CPUs competitive, higher energy efficiency, stronger ASIC resistance.
Thank you to everyone who voted and shared their views. Your participation helps guide the future of PEPEPOW. Stay tuned for more updates, and please join the discussion so we can reach a clearer consensus together.
The community vote on whether to switch PEPEPOWβs Proof of Work algorithm from XelisV2-pepew to HooHash V110 has now concluded.
Voting Results (2025/8/21 β 2025/9/4)
Discord: 50% Yes / 44% No / 6% Abstain (36 votes)
Twitter: 75% Yes / 0% No / 25% Abstain (4 votes)
Telegram: 55% Yes / 39% No / 5% Abstain (38 votes)
While βYesβ technically reached the 50% mark, the results are very close and opinions remain divided. This makes it difficult to claim a clear community consensus.
Next Steps
We will not proceed immediately with the change. Instead, the DAO will continue discussions and share clearer explanations of the pros and cons for everyone, especially focusing on the core question: Should PEPEPOW remain CPU-only, or move to a low-energy PoW that supports both GPU and CPU mining at near parity?
After this period of discussion, we will hold a second, more focused vote to confirm whether the community truly supports a change.
Why This Matters
Staying on XelisV2-pepew β CPU-only mining, simpler, keeps things as they are.
Switching to HooHash V110 β Enables GPU mining + keeps CPUs competitive, higher energy efficiency, stronger ASIC resistance.
Thank you to everyone who voted and shared their views. Your participation helps guide the future of PEPEPOW. Stay tuned for more updates, and please join the discussion so we can reach a clearer consensus together.
π3β€1π₯1π¦1
π’ PEPEPOW β Upcoming Discussion & Voting Announcement
Itβs been a quiet period, but PEPEPOW has never stopped evolving.
Starting next month, we will reopen community-wide discussions and may launch a new round of voting** based on the feedback collected. Topics include (but are not limited to):
πΉ PoW algorithm adjustments (efficiency, fairness, decentralization)
πΉ Roadmap refinements and next-phase development goals
πΉ Core / node improvements (sync, stability, miner experience)
To ensure the voting process is meaningful and aligned with community needs, we will proceed in stages:
1οΈβ£ Open Discussion & Feedback Collection
We invite miners, node operators, developers, and long-term holders to share:
* Recommended or preferred algorithms (with brief reasoning)
* Current issues or pain points (e.g., sync problems, mining experience)
* Development priorities or tools you want to see built
2οΈβ£ Drafting the Proposal Options
The dev team and community volunteers will consolidate all feedback into clear, structured proposals.
3οΈβ£ Formal Voting Expected Next Month
The exact time and mechanism will be announced separately.
Our goal: transparent decision-making driven by community consensus.
π§ Now is the best time to participate.
No hype β just real work, real consensus, and real development.
If youβre a:
Miner / Node Operator: Share your practical experience and issues
Developer: Provide technical insights or feasible solutions
Holder / Community Member: Help shape the long-term direction of PEPEPOW
π Share your thoughts in the channels.
Your input may directly influence the next era of PEPEPOW.
πΈ No hype, just work.
Itβs been a quiet period, but PEPEPOW has never stopped evolving.
Starting next month, we will reopen community-wide discussions and may launch a new round of voting** based on the feedback collected. Topics include (but are not limited to):
πΉ PoW algorithm adjustments (efficiency, fairness, decentralization)
πΉ Roadmap refinements and next-phase development goals
πΉ Core / node improvements (sync, stability, miner experience)
To ensure the voting process is meaningful and aligned with community needs, we will proceed in stages:
1οΈβ£ Open Discussion & Feedback Collection
We invite miners, node operators, developers, and long-term holders to share:
* Recommended or preferred algorithms (with brief reasoning)
* Current issues or pain points (e.g., sync problems, mining experience)
* Development priorities or tools you want to see built
2οΈβ£ Drafting the Proposal Options
The dev team and community volunteers will consolidate all feedback into clear, structured proposals.
3οΈβ£ Formal Voting Expected Next Month
The exact time and mechanism will be announced separately.
Our goal: transparent decision-making driven by community consensus.
π§ Now is the best time to participate.
No hype β just real work, real consensus, and real development.
If youβre a:
Miner / Node Operator: Share your practical experience and issues
Developer: Provide technical insights or feasible solutions
Holder / Community Member: Help shape the long-term direction of PEPEPOW
π Share your thoughts in the channels.
Your input may directly influence the next era of PEPEPOW.
πΈ No hype, just work.
β€3π₯1π1π«‘1π¦1
π’ PEPEPOW Development Progress & Roadmap Update
Hey everyone! Hereβs an update on what has been completed so far and whatβs coming next for the PEPEPOW ecosystem. Huge thanks to all contributors and community members pushing the project forward! ππΈβ‘
===========================
β Completed Development
===========================
β’ Website β Foztor, Edison, TrooperD
β’ Core Wallet (PePe-core) β Foztor
β’ Blockchain Explorer β Foztor, Edison
β’ Mining Pool β Foztor
β’ Miner (CPU/GPU) β Foztor
β’ Web Wallet β Beta β Foztor
β’ Dice Playground β Foztor
β’ API Server β near completion
β’ Mobile Wallet v1 β near completion
More details: π https://pepepow.org
===========================
π Next Phase Priorities
===========================
π· Wallets & User Experience
β’ Full non-custodial Web Wallet
β’ Mobile Wallet v1 public release
β’ Telegram Mini Wallet Bot
β’ PepewPay (one-page payment links / POS)
π· Developer Tools
β’ JS/TS SDK (pepew-js)
β’ ElectrumX Server
β’ Expanded API: sync, masternode data, inscriptions, more
π· On-chain Features
β’ PEPEW Inscriptions (Ordinals-style) + Viewer
β’ Masternode / Staking Tools & Dashboard
β’ Multi-Signature Vault Wallet
π· DeFi & Ecosystem Growth
β’ Minimal Oracle Gateway
β’ Liquidity Pool (wPEPEW on EVM or other chain)
β’ DEX Aggregator Integration
===========================
π€ Community Involvement
===========================
We welcome contributorsβdevelopers, designers, researchers, content creators, testers, and anyone who wants to help!
If youβre interested in participating, feel free to join discussions and share your ideas.
Even small contributions move the project forward.
Letβs keep building PEPEPOW together! β‘πΈπ
Hey everyone! Hereβs an update on what has been completed so far and whatβs coming next for the PEPEPOW ecosystem. Huge thanks to all contributors and community members pushing the project forward! ππΈβ‘
===========================
β Completed Development
===========================
β’ Website β Foztor, Edison, TrooperD
β’ Core Wallet (PePe-core) β Foztor
β’ Blockchain Explorer β Foztor, Edison
β’ Mining Pool β Foztor
β’ Miner (CPU/GPU) β Foztor
β’ Web Wallet β Beta β Foztor
β’ Dice Playground β Foztor
β’ API Server β near completion
β’ Mobile Wallet v1 β near completion
More details: π https://pepepow.org
===========================
π Next Phase Priorities
===========================
π· Wallets & User Experience
β’ Full non-custodial Web Wallet
β’ Mobile Wallet v1 public release
β’ Telegram Mini Wallet Bot
β’ PepewPay (one-page payment links / POS)
π· Developer Tools
β’ JS/TS SDK (pepew-js)
β’ ElectrumX Server
β’ Expanded API: sync, masternode data, inscriptions, more
π· On-chain Features
β’ PEPEW Inscriptions (Ordinals-style) + Viewer
β’ Masternode / Staking Tools & Dashboard
β’ Multi-Signature Vault Wallet
π· DeFi & Ecosystem Growth
β’ Minimal Oracle Gateway
β’ Liquidity Pool (wPEPEW on EVM or other chain)
β’ DEX Aggregator Integration
===========================
π€ Community Involvement
===========================
We welcome contributorsβdevelopers, designers, researchers, content creators, testers, and anyone who wants to help!
If youβre interested in participating, feel free to join discussions and share your ideas.
Even small contributions move the project forward.
Letβs keep building PEPEPOW together! β‘πΈπ
π4π2β1π₯1π¦1
π± PEPEPOW Android Wallet Release π
π Happy New Year 2026! π₯³
Wishing everyone a great year ahead!
After extensive development, testing, and refinement,
the PEPEPOW Android Wallet is now completed and officially released!
This marks an important milestone for the PEPEPOW ecosystem, enabling users to create and use a fully non-custodial PEPEPOW wallet directly on mobile, with fast and practical usability.
π Download & Release Notes (GitHub)
π [https://github.com/edisontw/pepepow-android-wallet/releases](https://github.com/edisontw/pepepow-android-wallet/releases)
---
β οΈ Important Notes (Please Read Carefully)
To avoid confusion or potential asset issues, please read the following carefully:
1οΈβ£ New wallet creation only
* This version does NOT support importing existing wallets
* Mnemonic recovery / restore is NOT supported
2οΈβ£ Back up your mnemonic securely
* The mnemonic generated on mobile must be saved immediately
* You may restore this mnemonic on the desktop wallet
* β οΈ Once the same mnemonic is used on desktop, do NOT continue using it on mobile, as this may cause balance inconsistencies
3οΈβ£ Default fast sync mode (FAST boot)
* Designed for fast usability, typically usable within ~20β30 seconds
* FULL SPV mode is only partially implemented, slow and still buggy, and not recommended
4οΈβ£ Security model
* Fully non-custodial
* Private keys / mnemonics remain on your device only
* API-based fast sync improves usability but never controls or holds user funds
---
This release is a stable and usable starting point.
Further improvements to SPV, sync logic, and user experience are planned.
Feedback, testing, and contributions are very welcome π
Thank you to everyone supporting and building PEPEPOW together β€οΈ
π Happy New Year 2026! π₯³
Wishing everyone a great year ahead!
After extensive development, testing, and refinement,
the PEPEPOW Android Wallet is now completed and officially released!
This marks an important milestone for the PEPEPOW ecosystem, enabling users to create and use a fully non-custodial PEPEPOW wallet directly on mobile, with fast and practical usability.
π Download & Release Notes (GitHub)
π [https://github.com/edisontw/pepepow-android-wallet/releases](https://github.com/edisontw/pepepow-android-wallet/releases)
---
β οΈ Important Notes (Please Read Carefully)
To avoid confusion or potential asset issues, please read the following carefully:
1οΈβ£ New wallet creation only
* This version does NOT support importing existing wallets
* Mnemonic recovery / restore is NOT supported
2οΈβ£ Back up your mnemonic securely
* The mnemonic generated on mobile must be saved immediately
* You may restore this mnemonic on the desktop wallet
* β οΈ Once the same mnemonic is used on desktop, do NOT continue using it on mobile, as this may cause balance inconsistencies
3οΈβ£ Default fast sync mode (FAST boot)
* Designed for fast usability, typically usable within ~20β30 seconds
* FULL SPV mode is only partially implemented, slow and still buggy, and not recommended
4οΈβ£ Security model
* Fully non-custodial
* Private keys / mnemonics remain on your device only
* API-based fast sync improves usability but never controls or holds user funds
---
This release is a stable and usable starting point.
Further improvements to SPV, sync logic, and user experience are planned.
Feedback, testing, and contributions are very welcome π
Thank you to everyone supporting and building PEPEPOW together β€οΈ
β€3π₯1π1
π PEPEPOW Non-Custodial Web Wallet β Now Live
Weβve completed the new PEPEPOW Non-Custodial Web Wallet, designed for security, simplicity, and future Telegram integration. This is the beginning of PEPEPOW going to the worlds.
Key highlights
π Non-custodial: mnemonic & private keys stay on the user side only
π§ Local signing (no server-side signing)
π Web wallet + Telegram Mini App share the same wallet core
βοΈ Backend only handles chain reading, fee estimation, and rawTx broadcast
π§© Modular architecture, easy to extend
This version is now open for testing & feedback.
Bug reports and suggestions are very welcome π
https://wallet.pepepow.net/
Weβve completed the new PEPEPOW Non-Custodial Web Wallet, designed for security, simplicity, and future Telegram integration. This is the beginning of PEPEPOW going to the worlds.
Key highlights
π Non-custodial: mnemonic & private keys stay on the user side only
π§ Local signing (no server-side signing)
π Web wallet + Telegram Mini App share the same wallet core
βοΈ Backend only handles chain reading, fee estimation, and rawTx broadcast
π§© Modular architecture, easy to extend
This version is now open for testing & feedback.
Bug reports and suggestions are very welcome π
https://wallet.pepepow.net/
β€2
## Telegram Announcement
π PEPEPOW Web Wallet Update β UTXO Consolidation Added
Weβve added a UTXO Consolidation feature to the PEPEPOW Web Wallet.
This allows users to merge many small UTXOs into a single output, helping to prevent the TRANSACTION TOO LARGE problem when sending funds.
π§ Why use consolidation
* Reduces transaction size
* Combines fragmented UTXOs
* Improves transaction reliability
β οΈ Important limitation
* Legacy addresses created without a mnemonic phrase are not supported in the Web Wallet
* These addresses cannot use the consolidation feature
β Recommended
Please generate a new address in the Web Wallet.
* Comes with a mnemonic (recovery phrase)
* Fully non-custodial
* Can be used permanently
* Supports consolidation and future features
π This feature is now available in the Web Wallet.
Feedback and testing reports are welcome.
π PEPEPOW Web Wallet Update β UTXO Consolidation Added
Weβve added a UTXO Consolidation feature to the PEPEPOW Web Wallet.
This allows users to merge many small UTXOs into a single output, helping to prevent the TRANSACTION TOO LARGE problem when sending funds.
π§ Why use consolidation
* Reduces transaction size
* Combines fragmented UTXOs
* Improves transaction reliability
β οΈ Important limitation
* Legacy addresses created without a mnemonic phrase are not supported in the Web Wallet
* These addresses cannot use the consolidation feature
β Recommended
Please generate a new address in the Web Wallet.
* Comes with a mnemonic (recovery phrase)
* Fully non-custodial
* Can be used permanently
* Supports consolidation and future features
π This feature is now available in the Web Wallet.
Feedback and testing reports are welcome.
β€6π1π¨βπ»1
π PEPEPOW Telegram Wallet (Mini App) β Open for Testing
PEPEPOW keeps moving forward.
You can now try the PEPEPOW Telegram Wallet Mini App:
π @pepepow_walletbot
π Non-Custodial
* Keys and mnemonic stay on your device
* Local transaction signing only
π Extra Telegram Feature
* Send PEPEW directly to other Telegram users
π What the server stores
* Telegram ID
* Default PEPEPOW address
(No keys, no mnemonics)
π Please save your mnemonic phrase carefully.
π User guide:
https://github.com/edisontw/pepepow-wallet-suite/blob/main/docs/telegram-user-guide.md
Found a bug or have suggestions? Feedback is welcome.
Developers are invited to explore and build.
PEPEPOW keeps moving forward.
You can now try the PEPEPOW Telegram Wallet Mini App:
π @pepepow_walletbot
π Non-Custodial
* Keys and mnemonic stay on your device
* Local transaction signing only
π Extra Telegram Feature
* Send PEPEW directly to other Telegram users
π What the server stores
* Telegram ID
* Default PEPEPOW address
(No keys, no mnemonics)
π Please save your mnemonic phrase carefully.
π User guide:
https://github.com/edisontw/pepepow-wallet-suite/blob/main/docs/telegram-user-guide.md
Found a bug or have suggestions? Feedback is welcome.
Developers are invited to explore and build.
π5
π Community Update: PoW Direction & Next Vote
The previous PoW vote was very close. While βYesβ passed 50%, it did not show clear consensus.
β Some prefer to stay on XelisV2 for stability and CPU-only mining.
Others support HooHash for better energy efficiency, ASIC/FPGA resistance, and restoring GPU mining while keeping CPUs competitive.
To move forward responsibly, we will:
Share clearer explanations in general chats
Then hold a second, simpler vote focused on the core question
πThe Real TL;DR Question
To simplify things, the core decision is essentially this:
Should PEPEPOW remain a CPU-only coin, or move to a low-energy PoW that supports both GPU and CPU mining at roughly equal parity?
This framing avoids deep technical details and focuses on the practical impact on miners, the network, and future growth.
πNo technical changes will happen without stronger community agreement.
The previous PoW vote was very close. While βYesβ passed 50%, it did not show clear consensus.
β Some prefer to stay on XelisV2 for stability and CPU-only mining.
Others support HooHash for better energy efficiency, ASIC/FPGA resistance, and restoring GPU mining while keeping CPUs competitive.
To move forward responsibly, we will:
Share clearer explanations in general chats
Then hold a second, simpler vote focused on the core question
πThe Real TL;DR Question
To simplify things, the core decision is essentially this:
Should PEPEPOW remain a CPU-only coin, or move to a low-energy PoW that supports both GPU and CPU mining at roughly equal parity?
This framing avoids deep technical details and focuses on the practical impact on miners, the network, and future growth.
πNo technical changes will happen without stronger community agreement.
β€1
Should PEPEPOW move from CPU-only mining to a low-energy PoW that supports both CPU and GPU mining?
Final Results
91%
Yes β CPU + GPU mining (HooHash)
8%
No β Stay CPU-only (XelisV2)
1%
Abstain
π3β€1