3NUM.ethConnecting 5 Billion Mobile Subscribers to Web3 With 3NUM’s Decentralized Telephony Bridge
3NUM provides users with the world’s first Web3 Mobile Number minted as a NFT, called a 3NUM Shield. These globally routable mobile numbers are created as persistent identifiers on the blockchain, giving users complete control of their web3 messaging identity. 3NUM users can securely communicate with one another via 3NUMs encrypted messaging protocol without relying on traditional telecom providers while also being able to communicate with traditional phone numbers via 3NUMs decentralized tel...
3NUM.ethBringing Avvy Domain Support to Signal.web3
Our team is a big fan of Avalanche! From its EVM compatibility, to its subnet architecture, speed and incredibly reasonable transaction fees- it’s clear why the chain has become so successful. That is why we are so excited to announce that we’re extending the functionally of Signal.web3 to support Avvy Domains, allowing users to lookup and message Signal contacts with .avax names! We made Avvy our priority as the next web3 name to support in Signal.web3, as we think it will be a great additio...
3NUM.ethΞNUM Messaging NFTs
At the heart of the ΞNUM solution is our novel messaging NFT, called an ΞNUM. ΞNUMs are a new utility NFT that exists as a new “communications identifier”. An ΞNUM can be thought of as a modernized, Web3 phone number, that also doubles as a real-world phone number. Its inherent superpower is extending truly end-to-end encrypted messaging to current Web3 identifiers like Ethereum Name Service (ENS) and wallet addresses. ΞNUMs are constructed so they can be minted on any layer 1 or layer 2 bloc...
Your Shielded Web3 Messaging ID 3NUM Shield is the first Web3 mobile number minted as a NFT that protects your identity and provides privat
3NUM.ethConnecting 5 Billion Mobile Subscribers to Web3 With 3NUM’s Decentralized Telephony Bridge
3NUM provides users with the world’s first Web3 Mobile Number minted as a NFT, called a 3NUM Shield. These globally routable mobile numbers are created as persistent identifiers on the blockchain, giving users complete control of their web3 messaging identity. 3NUM users can securely communicate with one another via 3NUMs encrypted messaging protocol without relying on traditional telecom providers while also being able to communicate with traditional phone numbers via 3NUMs decentralized tel...
3NUM.ethBringing Avvy Domain Support to Signal.web3
Our team is a big fan of Avalanche! From its EVM compatibility, to its subnet architecture, speed and incredibly reasonable transaction fees- it’s clear why the chain has become so successful. That is why we are so excited to announce that we’re extending the functionally of Signal.web3 to support Avvy Domains, allowing users to lookup and message Signal contacts with .avax names! We made Avvy our priority as the next web3 name to support in Signal.web3, as we think it will be a great additio...
3NUM.ethΞNUM Messaging NFTs
At the heart of the ΞNUM solution is our novel messaging NFT, called an ΞNUM. ΞNUMs are a new utility NFT that exists as a new “communications identifier”. An ΞNUM can be thought of as a modernized, Web3 phone number, that also doubles as a real-world phone number. Its inherent superpower is extending truly end-to-end encrypted messaging to current Web3 identifiers like Ethereum Name Service (ENS) and wallet addresses. ΞNUMs are constructed so they can be minted on any layer 1 or layer 2 bloc...
Your Shielded Web3 Messaging ID 3NUM Shield is the first Web3 mobile number minted as a NFT that protects your identity and provides privat
Subscribe to 3NUM.eth
Subscribe to 3NUM.eth
Share Dialog
Share Dialog
<100 subscribers
<100 subscribers
We love Signal. It is the most trusted end-to-end encrypted messaging platform available, with over 40 million users. We believe that the future of communication is end-to-end encrypted, and the Signal protocol is the clear choice for ensuring that reality. But, as equal enthusiasts of both Signal’s encrypted messaging protocol and Web3, we think there is an opportunity for these two to intersect and create an even better experience than we currently have. For this reason we are investing our time into making Signal Web3 native.
It will make Signal even more secure than it already is
It will add new functionality that Web3 enthusiasts will routinely use and leverage, further increasing Signal’s clear competitive advantages.
Because Signal is open source, we are able to build Web3 features and submit them as pull requests to integrate directly into the Signal platform. We know some of these pull requests will not be accepted by the Signal Foundation (for example, this one), so we will maintain a fork of Signal with Web3 functionality that fully interoperates with the existing Signal ecosystem.
Web3 Names and Addresses
We have built and released the ability for users to look up and message one another with their ENS name in Signal. We will continue adding support for leading blockchain name providers, including Avvy, Unstoppable Domains and Bonfida (Solana), so users can look up and message one another knowing only their blockchain-registered web3 name. In addition to web3 name lookups, we will build and support this same functionality for wallet addresses. The ENS lookup service we built was the first pull request submitted to the Signal Foundation, and it was not accepted, prompting us to create and maintain a Web3 fork of Signal.
Expand Identifiers Used for Account Verification
Signal currently relies on a user's phone number to identify their “account” within Signal. Unfortunately, this dependency leaves users vulnerable to SIM swap attacks. We believe this is problematic, and thus we will build the ability to identify a user's Signal account with a Web3 native identifier, secured by their private keys, rather than a traditional phone number, adding additional security for existing Signal users.
Wallet Support
In addition to identifying users with a Web3 address, we will also add native wallet support. This feature greatly expands our ability to build extended user functionality, including wallet messaging and payments all within the same application. We will build integrations with existing APIs so users can do peer to peer payments with popular cryptocurrencies like ZCash.
More to Come
While we have plans to enhance Signal beyond these feature sets, the scoped work listed above will take the majority of our time for the foreseeable future.
Our development team will continue building out these features and submitting them as pull requests to the Signal Foundation in order to make Signal Web3 native. It is important to point out that users on our maintained Web3 version of Signal will be able to communicate seamlessly with the 40 million users on the existing Signal platform.
We are committed to ensuring that our maintained version of Web3 Signal is fully open sourced and public. You can stay current with our development efforts by joining our Discord channel or by viewing our public Github repo.
If endeavor sounds interesting to you, and you would like to contribute, please join our Discord channel to get in touch with us!
Follow us on Twitter by clicking here
We love Signal. It is the most trusted end-to-end encrypted messaging platform available, with over 40 million users. We believe that the future of communication is end-to-end encrypted, and the Signal protocol is the clear choice for ensuring that reality. But, as equal enthusiasts of both Signal’s encrypted messaging protocol and Web3, we think there is an opportunity for these two to intersect and create an even better experience than we currently have. For this reason we are investing our time into making Signal Web3 native.
It will make Signal even more secure than it already is
It will add new functionality that Web3 enthusiasts will routinely use and leverage, further increasing Signal’s clear competitive advantages.
Because Signal is open source, we are able to build Web3 features and submit them as pull requests to integrate directly into the Signal platform. We know some of these pull requests will not be accepted by the Signal Foundation (for example, this one), so we will maintain a fork of Signal with Web3 functionality that fully interoperates with the existing Signal ecosystem.
Web3 Names and Addresses
We have built and released the ability for users to look up and message one another with their ENS name in Signal. We will continue adding support for leading blockchain name providers, including Avvy, Unstoppable Domains and Bonfida (Solana), so users can look up and message one another knowing only their blockchain-registered web3 name. In addition to web3 name lookups, we will build and support this same functionality for wallet addresses. The ENS lookup service we built was the first pull request submitted to the Signal Foundation, and it was not accepted, prompting us to create and maintain a Web3 fork of Signal.
Expand Identifiers Used for Account Verification
Signal currently relies on a user's phone number to identify their “account” within Signal. Unfortunately, this dependency leaves users vulnerable to SIM swap attacks. We believe this is problematic, and thus we will build the ability to identify a user's Signal account with a Web3 native identifier, secured by their private keys, rather than a traditional phone number, adding additional security for existing Signal users.
Wallet Support
In addition to identifying users with a Web3 address, we will also add native wallet support. This feature greatly expands our ability to build extended user functionality, including wallet messaging and payments all within the same application. We will build integrations with existing APIs so users can do peer to peer payments with popular cryptocurrencies like ZCash.
More to Come
While we have plans to enhance Signal beyond these feature sets, the scoped work listed above will take the majority of our time for the foreseeable future.
Our development team will continue building out these features and submitting them as pull requests to the Signal Foundation in order to make Signal Web3 native. It is important to point out that users on our maintained Web3 version of Signal will be able to communicate seamlessly with the 40 million users on the existing Signal platform.
We are committed to ensuring that our maintained version of Web3 Signal is fully open sourced and public. You can stay current with our development efforts by joining our Discord channel or by viewing our public Github repo.
If endeavor sounds interesting to you, and you would like to contribute, please join our Discord channel to get in touch with us!
Follow us on Twitter by clicking here
No activity yet