Diegorb1329/eth_magicians_forum huggingface dataset:
Title: Improving_GasEstimation
Category: Web

Author: ligi
Date: 2020-01-08T12:05:05.067Z

Currently estimateGas has a practical problem. It can happen that you estimate gas for a transaction and then sign a transaction with this limit and this transaction fails with out of gas. E.g. caused by other transactions to the same contract in the meantime.
MetaMask mitigates this by multiplying 1.5 to the estimated gas (and limiting to 0.9xBlockGas limit)
These are kind of ugly magic constants and the system does not feel nice.
This thread is to collect ideas on how to improve on the situation. One idea could be that this multiplier can be influenced with NatSpec (cc @chriseth) as the author of the smart-contract function might have a better magic number than 1.5. Ideally we get away from magic numbers after all - but I am currently having no good idea on how to do so.
Would also be happy about the experiences/magic numbers of other wallets here.

Author: mcdee
Date: 2020-01-08T21:46:38.286Z

If you’re after a “safe high” gas limit then perhaps having a different call that carried out accounting a little differently would be interesting.  Charging 20K for each SSTORE rather than the sometimes-5K-sometimes-20K would be an obvious tweak.
This wouldn’t catch everything, of course, but could help with one situation where gas estimation fails.
Title: _Meta__UX_research_and_user_studies_results
Category: Web

Author: Tbaut
Date: 2018-11-20T15:52:00.034Z

We share our code on Github, our thoughts and passion during gatherings… now let’s share user studies and UX research results here!
In my opinion, crypto-products should not embed any tracking tool whatsoever. A good way to (try to) understand our users without compromising their privacy is to perform user studies and UX researches.
This post is meant to be a place where we share the results and findings from UX and user studies conducted on wallet products. It can obviously be your own product or simply articles you found on the web.

Author: Tbaut
Date: 2018-11-20T15:52:09.212Z

I’ll kick off with a great article from @ale: https://medium.com/design-for-crypto/ðapp-user-experience-audit-afc11e4384c3

Author: Tbaut
Date: 2018-11-20T17:39:38.972Z

@deltajuliet has posted the results of a survey made on this forum, get it here.

Author: beltran
Date: 2018-11-21T23:54:55.887Z

hey @Tbaut I think that you will have a lot materials to dig into, also with practical actionable insights on
http://discuss.conflux.network
which is a exclusively Design oriented EM forum 
People have shared a lot of insights also on the process as did @hester @patbowen from Status
http://discuss.conflux.network/t/design-driven-projects-status/196
on our side, for the Web3 Design System projects, (guidelines + library of Web3 components)
we are interviewing developers, designers, product people, anyone who has talked to users, and possibly users themselves.
We will have insights to share in January
but we showed something at Devcon, and when the recording for the Web3 design system panel comes out I’ll share it here as well
Let us know what you find
Title: INCUBED_servers_as_onion_services
Category: Web

Author: ligi
Date: 2018-11-04T14:37:37.370Z

Inspired by INCUBED and Peters talk - what do you think of INCUBED servers as onion services to get a more privacy preserving web3?
PS: also makes running these servers easier as you do not need external ip/to configure your router/…

Author: ligi
Date: 2018-11-06T13:29:34.379Z

Some motivation (this can be one of the umbrellas he is talking about):
https://www.reddit.com/r/ethereum/comments/9u5sm8/devcon4_cory_doctorows_eff_boingboing_riveting/
About INCUBED: https://www.youtube.com/watch?v=Ug9Nte1xwv4

Author: ligi
Date: 2019-07-20T16:46:16.462Z

now found some time to work on that project at the flying circuit hackathon. Find the project here: https://github.com/tincubeth
Title: Dapplets__part2___project_status_and_standard_arch
Category: Web

Author: Ethernian
Date: 2019-07-08T10:03:36.691Z

Hello friends,
I was quite silent here because I am working on Dapplets Project now.
We have implemented some new cool stuff and made (may be controversial?) decision choices.
Before the current development phase gets finalized, I would very appreciate all your thought and any feedback.
Please find the main article here:
Dapplets (part 2): implementation details and development status
thank you!
Title: Video_archive_from_the_ETHBerlin_UX_Unconference__
Category: Web

Author: jpitts
Date: 2018-09-10T15:44:55.906Z

https://www.youtube.com/watch?v=MaloR0gGQWg
Title: Dapplets_SOWA___Secured_Open_Wallet_Architecture
Category: Web

Author: Ethernian
Date: 2020-02-27T02:51:00.757Z

Hello All the Magicians,
A long time ago I published a thread and a medium article
Dapplets: Rethinking Dapp Architecture for better adoption and security.
While we are mostly focused on the Dapplets project, we have decided to split-off the Wallet related part of it into the separate project S.O.W.A. - Secured Open Wallet Architecture.
Articles:
Part 1: Introducing S.O.W.A. – Secured Open Wallet Architecture
Part 2: Implementing S.O.W.A. – Secured Open Wallet Architecture
What is it about?

S.O.W.A. — is a general chain agnostic standard for scripts running in the Wallet’s sandbox and describing both the confirmation View and the Action execution plan.

What is the advantage?

Interoperability between Wallets.
WYSIWYS Views.
Suitable for a wide range of hardware and security requirements.
Modular and extensible architecture.
Transaction batching (User confirms one Action starting many transactions).
Allows gas payments for infrastructure providers like Wallets, Bridges and Relays
Easy to audit; explicit specifications and audit status.

We have started work on S.O.W.A. because we need the standard for our Dapplets project and believe it would be useful for many other projects too.
Our work is still in progress, but we hope to start a discussion between Wallets and DApp developers to create new standards for better UX and interoperability.
Acknowledgements
A lot of thanks to @danfinlay, @JamesZaki and @ligi for their support and feedback!
Title: Resulting_from_action_item_at_wallet_working_group
Category: Web

Author: ligi
Date: 2018-09-20T09:05:40.431Z

please add your wallets here: https://github.com/ethereum-wallets/ethereum-wallet-list
also please let me know what fields you think are missing. Currently mainly focusing on the fields that I need for the android library that resolves wallets on given constraints.
Also searching people to champion the iOS and web side - currently focused on Android - but this also might make sense to have it for other platforms.
Title: Dapplets__Challenges_while_creating__sound_and_com
Category: Web

Author: Ethernian
Date: 2019-03-26T23:44:08.262Z

Today I had a brainstorming about ways to create a secure Wallet UI representing transactions in a “sound and complete” way. Where the “Sound UI” should prevent Views from rendering misleading representation, and the “Complete UI”  means an ability to define a “sound” View for any given type of data (pictures+text).
We came to conclusion, that existing Layout Managers implementation were built without “soundness” in mind: it is possible to supply specially prepared data, moving visual elements into invisibility at least partially (and without any notification for the user). Looks like the silent cropping of the visual representation is considered as not that bad.
Dear Wallet Devs: is the problem real? Do you use your own Layout Manager and Renderer to prevent misleading representations or you trust the usual one?
Title: Building_a_library_of_Web3_Design_Patterns_for_Dev
Category: Web

Author: dcardines
Date: 2022-11-06T12:46:20.089Z

As the title says I’m building a library of Web3 design pattern resources.
Built it because as I was designing for a DAO certain web2 design patterns didn’t make sense for the blockchain, and I ended up having 5 dApps open just to check how the UX of depositing liquidity worked.
This is for designers and devs alike.
If you guys want to help improve the state of UX of crypto, can I ask that you:

Use the site
Suggest dApps that I can add to the library
Spread the word
Support the site by being a paying subscriber in the future
Suggest ways for it to be improved




Yep.so



Build a landing page in 2 minutes.
Say goodbye to complex landing page builders. Meet Yep — the free, AI-powered no-code landing page builder. Convert visitors to paying customers.





Thanks a lot.
Title: เร_ยนร__และค_นคว_า
Category: Web

Author: OhArthit
Date: 2021-03-01T21:06:43.108Z

Continuing the discussion from A general-purpose L2-friendly ENS standard:

Author: jpitts
Date: 2021-03-02T09:05:53.796Z

Could you entitle this more appropriately? It is fine to use a non-English language but the title should offer a translation and describe the specific topic.
Title: CAIP_24__A_proposal_for_protocol_agnostic_provider
Category: Web

Author: danfinlay
Date: 2020-10-23T21:13:01.178Z

I’m sure we’re all thinking about how dapps will connect to wallets in a multi-network world, so let’s have that conversation.
I’ve written an initial draft on the CAIPs repo as CAIP-24. It’s a very simple starting point, but is very extensible, and I think should be fairly straightforward to adapt to and from other JSON-RPC based approaches.
https://github.com/ChainAgnostic/CAIPs/pull/24

Author: dominic
Date: 2020-10-27T10:58:49.718Z

Thanks @danfinlay. Reading through this I also found CAIP-25 and totally rabbit holed into that which is super cool as well and seems to solve: https://github.com/MetaMask/metamask-extension/issues/1820 ?!
Title: New_to_the_space__Looking_to_pick_up_a_small_proje
Category: Web

Author: jayhxmo
Date: 2021-03-31T21:40:58.603Z

Hi,
My name is Jay Mo and I’m a product designer working for a Bay Area startup. I’ve been interested in the blockchain space for a while, but never had the time to dig deeper. I thought the best and most fun way to do this would be by picking up a small project, creating a lot, and getting feedback through it. 
Do you know anyone who’s looking for design help?

Author: jpitts
Date: 2021-04-02T08:09:49.293Z

What kind of skills do you have?
Many discussions on this Forum are low-level, for example: changes to how the virtual machine functions, or how state data is stored. However, some proposals and discussions would have UI / UX implications, and might benefit from design brainstorming and prototyping.
For example, this ERC-3450 proposal by @dstreit; this is cryptography-related, but has UI implications because it helps users secure their funds from key loss. Maybe the proposal could use some UI mockups or a demo.
To get into the weeds: ERC-3450 is a standard way to split a BIP39 mnemonic / word phrase into another set of mnemonics which can then be distributed to other parties for safe-keeping. Later, a predetermined number of them could be brought together to reproduce the original BIP39 mnemonic / word phrase. Check out the JS module implementation: danielstreit/shamir-bip39

Author: kladkogex
Date: 2021-04-02T13:57:50.917Z

Hey Jay -
At SKALE we are looking for a long-term maintainer to help us maintain SKALE website
skale.network
We can issue a long term token grant
Title: Window_ethereum_disable___for_logging_out_of_provi
Category: Web

Author: miguelmota
Date: 2019-09-06T15:04:46.366Z

Currently web3 providers offer an .enable() method for allowing the dapp to connect but there doesn’t exist a method to disconnect. Standardizing around a .disable() method on the provider would allow dapps to display a logout button if this disable method is available. This would be beneficial for providers that offer standard login experiences like Portis, Squarelink, Authereum, etc. and as a dapp developer you don’t have to think about how to handle logging out for each provider. I believe web3connect does something similar with a .close() method on the provider.
What are your thoughts on standardizing around an optional .disable() method on the provider for disconnecting and logging users out of the provider on the dapp?

Author: wighawag
Date: 2019-09-18T15:38:16.845Z

Hi @miguelmota
I agree this would be useful. I actually proposed the same thing to be added to 1102 :  EIP-1102: Opt-in provider access

Author: EvilJordan
Date: 2020-06-24T19:42:58.977Z

Following up here… Obviously disable() hasn’t yet made it to the library, but are there any proven methods to disconnect?
If not… how does one disconnect for testing purposes? I don’t see anything in the local browser indicating ethereum is “active”.

Author: NellalinkHQ
Date: 2020-09-22T23:51:24.674Z

We kindly await this feature
Title: Improving_Multisig_Wallet_Standards
Category: Web

Author: iamcapote
Date: 2024-08-01T20:44:33.349Z

A multisig wallet is a smart contract-based wallet that requires multiple signatures to execute transactions. This mechanism enhances security by distributing control among multiple parties. However, there are areas for improvement to further secure and democratize the governance of multisig wallets, especially within decentralized autonomous organizations (DAOs).
Proposed Improvements to the Multisig Standard
1. Time-Based Voting Shares
Problem Statement: Many DeFi protocols are managed using multisig wallets, which control the distribution of funds and participate in critical protocol decisions. Currently, there is no effective mechanism to remove bad actors from the core governance of a DAO if they form a majority within the multisig group or a majority within the community
Solution: Implement an election-based multisig process to address the issue of entrenched bad actors. This proposal includes the following features:

Regular Elections: Members of the multisig wallet are elected by the community every four years. This process ensures that the control of the wallet remains in the hands of trusted and accountable members.
Presidential Role: The multisig can have a president or owner, who may be chosen on a different schedule from other members or this role may not be voted on at all. This role provides an additional layer of oversight and leadership.
Community Involvement: This standard allows the community to have an equal opportunity to influence the future of their platform through regular elections.

Not every DAO will require this standard, but it offers a democratic method for those that prioritize community governance.
This standard can also be incorporated with:
2. Time-Locked Transactions
Feature: Allow owners to set time delays on certain transactions.
Benefit: Provides a window to cancel potentially malicious transactions, enhancing the security and control over high-value or sensitive transactions.
3. NFT Tokenized Shares
Feature: Represent ownership shares in the multisig wallet as NFTs.
Benefit: Facilitates the distribution and transfer of ownership rights, making it easier to manage changes in ownership. Tokenized shares enable seamless transfer and management of ownership stakes, promoting flexibility and liquidity.
Note: This is an open proposal inviting any developer to create what is described here  credit would be nice thank you

Author: kopykat
Date: 2024-08-11T11:46:43.959Z

Hey, have you checked out modular smart accounts (ERC-7579)? Safe and other existing smart accounts are compatible and you can build modules that enable these features
Title: Web3_Providers_for_the_Future
Category: Web

Author: andytudhope
Date: 2018-05-17T00:01:49.814Z

I would like to start a thread about injecting web3 providers and what the plans are for that going forward, especially given this interesting piece from the one and only @ricburton:
https://medium.com/@ricburton/metamask-walletconnect-js-b47857efb4f7
We just added a way for DApps to identify that it is a Status client which is the provider here: [#4227] Allow DApps to identify status host by jeluard · Pull Request #4233 · status-im/status-mobile · GitHub
And think this is an interesting and good topic to pick up across the ecosystem which might also dovetail well into better and more secure signing schemes in general.
Would love to get @danfinlay’s input too.

Author: danfinlay
Date: 2018-05-20T03:55:35.585Z

My current best ideas on this topic have been captured in this proposal:




EIP-1102: Opt-in provider access EIPs


    Hi everyone. My name is Paul Bouchon and I recently joined the MetaMask team. 
MetaMask and most other tools that provide access to Ethereum-enabled environments do so automatically and without user consent. This exposes users of such environments to fingerprinting attacks since untrusted websites can check for a provider object and reliably identify Ethereum-enabled clients. 
This proposal outlines a new dapp initialization strategy in which websites request access to an Ethereum provider API i…
  

Sorry for not seeing this first, it would have been a good place for outlining the constraints in public before sharing a proposal, please add any constraints there that (any reader here) feels we’ve missed.

Author: ricburton
Date: 2018-05-21T15:31:48.877Z

This is fantastic. I definitely want to make sure all of this infrastructure is shared and available on all wallets.
We should compete on approaches and focus. In my mind: Balance wants to become a bank. Status wants to take aim at Facebook. Metamask is the most pragmatic tool to kick off desktop dapp development.

Author: p0s
Date: 2018-11-29T12:59:14.832Z

I know this thread is older, but we finally opened a Provider Ring for more structured (dis)agreement on topics like EIP1102: https://ethereum-magicians.org/c/working-groups/provider-ring
Title: Multi_chain_Ethereum_Provider
Category: Web

Author: pedrouid
Date: 2021-08-26T12:01:39.824Z

EIP-1193 was a huge step for interoperability on Ethereum. Provider diversity exploded when EIP-1193 started being adopted and the line between integrating Metamask and WalletConnect became unnoticeable. Other providers followed and we saw many others showing up after. It also made possible for different developer libraries to exist like web3-react, Web3Modal and Blocknative’s onboard.js.
However this standard is explicitly designed for a single chain to be connected to which makes it very rigid and cumbersome in the current accelerating pace of L2 adoption and other EVM chains
In my opinion, there is a need for a new standard for Multi-Chain Ethereum Provider that is able to interface with multiple chains simultaneously therefore a wallet can expose accounts for different chains simultaneously as well. Additionally this would require that each JSON-RPC request is also targeted at a specific chainId.
EIP-1193 has already built much of the ground work for a new provider standard to exist and the existence of a Multi-Chain Ethereum Provider could easily eliminate for users to switch chains on their wallet based on dapp requirements
I would love to include in this discussion all the wallet providers but also javascript library developers.
cc @greg @ricmoo @danfinlay @rekmarks @NoahZinsmeister @lukasschor @itamarl @brunobar79

Author: greg
Date: 2021-08-26T14:23:07.365Z

I’m on mobile and not really thinking it totally through but Why not just extend the base 1193 to incorporate the addChain method included in metamask across every other wallets.
You could just emit something like requestChangeNetwork
The only thing that might be frustrating is managing multiple providers but perhaps I’m over thinking how wallets manage them.
Title: DAPP_UX___adoption_unconf_in_Prague__June_30_
Category: Web

Author: JosefJ
Date: 2018-05-21T16:40:15.618Z

Hi everyone,
as I mentioned at the web3 UX unconf, I’m organizing a followup UX event in Prague this June.
To goal of the event to learn from each other’s approaches, share best practices and find a way to collaborate in order to bring all of those groundbreaking apps to masses.
The event is happening in the Institute of Cryptoanarchy in Prague, on the June 30. It’s a free one day invite-only event which will publicly live-streamed.
The event is locked, for now, to first secure spots for people working on relevant projects:
https://www.eventbrite.com/e/dapp-dapps-adoption-paralelni-polis-tickets-45977833939
If you wish to present or attend, please let me know here or via josef@polynom.com and I’ll send you the password.
If you will be in Prague before and after the event, I’ll also organize the following sides:
Friday, June 29
Intro dinner/drinks
Saturday, June 30
The event itself.
After unconf dinner
Sunday, July 1
Open panel and working session
If you wish to stay in Prague and you are looking for a workspace, let me know and I can get you a spot in the Institute or Paper Hub co-work in the same building.
Any suggestions are welcomed.

Author: okwme
Date: 2018-06-27T15:31:21.583Z

Hi,
Last minute but I’d like to come!
Is the best method of reserving to use https://dapp.polynom.com/ ?

Author: JosefJ
Date: 2018-06-27T15:46:03.430Z

Yes! That way you get the whole experience
Title: Is_there_a_good_standard_for_time_decaying_multisi
Category: Web

Author: SoundMoney
Date: 2022-09-03T19:17:04.897Z

I’d like to implement the following multisig smart contract:

2/3 multisig until time T
At time T the multisig becomes a 1/3
Any signer can increase T

I only want to store ETH for now, but ERC20 support would be a plus.
Would appreciate any code pointers!
Also open to philosophical feedback as to whether this is a good vault. I like it because the vault is not less secure than a standard 2/3 multisig as long as T is extended frequently. And if the owner loses 2 keys, they can recover the vault after T as long as nobody else knows any of the keys.

Author: Pandapip1
Date: 2022-09-03T23:14:38.207Z

Personally, I would have the following properties on it:

Can send ether and submit arbitrary transactions
When a key is used, a time delay is set to remove that key from the multisig altogether. This gets cleared when a new time delay for that key is set.
New keys can be added and old ones removed with a 2/3 supermajority (rounded down)
Keys can remove themselves

Author: TimDaub
Date: 2022-09-04T09:54:56.343Z

I could imagine EIP-4973 to be helpful here. Among themselves, the parties could “give” or “take” account-bound tokens" that signal membership over a shared account. A contract holding the funds could then be set up such that for withdrawing Ether, a quorum of ABT holders would have to accept the transfer. Additionally, it could be set up where any holder of the ABT may increase T.
Title: Trustless_userop_signing_via_browser_
Category: Web

Author: mac
Date: 2023-10-12T20:24:33.661Z

The setup:
Web developer Bob wants to build a web game using web standards, and Bob doesn’t want to require users to install browser extensions. Bob decides to use eip4337 to create accounts for all his players.
The Question:
How should Bob’s web app display a userop to be signed by a user (the sender: Alice) – without using a browser extension or window.ethereum, such that Alice can know Bobs web app isn’t doing a bait and switch?
And to make the convo realistic – let’s assume Alice doesn’t want to give Bobs web app access to the her ecdsa priv key
As an example:
WebAuthN based wallets wanting to get users to sign will send the userop struct as the Challenge in a webauthn.credentials.get() call. When the browser mediated modal pops to sign, it doesn’t show what you are signing – so how does the user trust this?
10000197481516×698 125 KB
Title: Wallet_PSA__Beacon_Chain_Withdrawal_Address_Balanc
Category: Web

Author: timbeiko
Date: 2023-02-28T22:21:47.040Z

Cross-posting from Twitter, to reach folks here as well:

Shapella PSA for wallet devs: beacon chain withdrawals don’t create a transaction on the EL. This means that if you’re scanning incoming txns to an address to update its balance, you won’t process withdrawal balance updates


We saw this bug on MetaMask during the Sepolia fork, but others probably have the same issue. Here’s a bug report for them: [Bug]: ETH balance not updating after Beacon Chain Withdrawals · Issue #17936 · MetaMask/metamask-extension · GitHub


Withdrawals are processed similarly to PoW emission: they are added to the addresses’ balance “behind the scenes”, at the end of block execution. See the State Transition section here: EIP-4895: Beacon chain push withdrawals as operations


If you want to run your own validator to test this, you can do so on Zhejiang: https://zhejiang.ethpandaops.io Alternatively, you can track the Sepolia validators and their periodic withdrawals. Goerli date fork isn’t set yet, but we’ll likely do so on ACDE this Thursday.
Title: User_initiation_problem
Category: Web

Author: jassmin
Date: 2023-08-24T11:59:12.106Z

I think Ethereum’s switch from PoW to PoS was a historic moment and a triumph of the entire community. However I worry for a following case and haven’t found a solid answer for it.
Suppose that there’s a user who doesn’t have any access to exchanges and there’s no one who owns any ETH or even they might not have the access to any ETH.
In PoW, perhaps the one can leave the PC long enough period running the blockchain client to mine or even join a mining pool and can own his first native asset which can be used to pay for transaction. From there, the user can start acting in the network.
But in the current PoS setting Ethereum is in, I don’t see any way a user could independently initiate onchain actions. For him to begin in blank slate, he MUST get his first ETH from others by any means.
Is there anyone thinking about this problem? Or is it even a problem to worry? Or, does anyone have a solid and convincing answer to this?

Author: Mani-T
Date: 2023-08-25T09:32:27.584Z

In a Proof of Work (PoW) system, acquiring the necessary hardware to mine or joining a mining pool incurs a certain cost, whereas in a Proof of Stake (PoS) setting like Ethereum’s current state, staking is required, which also involves a form of investment. The fundamental concept in both cases is that participation in the network requires some form of commitment, whether it’s computational power in PoW or staked assets in PoS. So I don’t think this is a problem to worry.
Title: Membership_proof_in_a_Merkle_Tree_with_Peer_Secret
Category: Web

Author: axe
Date: 2020-01-07T15:56:35.190Z

Starting a new topic to discuss the implementation of a pseudo anonymous membership proof in a Social Recovery Process. see: ERC2429
Problem: In a recovery the peers will have theirs addresses link to the user in recovery. Privacy and accounts correlations is something all users should be aware and as possible the system should have mechanism to help in privacy matters.
To mitigate this problem in the context of ERC2429, I think will be beneficiary to include a extension as how the Merkle tree is build.
One solution is to generate new Accounts for each recovery contract, mitigating the potencial link between accounts. But this solution put more pressure on the peer, that will have to manage more keys. As the recovery process is something unusually done, there is a probability of keys getting lost.
The proposed solution is something like a barebone HD Wallet strategy.

The user setting a Recovery contract has to generate a peer_Hash (ERC2429).
The peer uses this peer_hash with their private key.
Following something like NewPublicKey = PrivateKey * Secret * G

When is needed a recovery process, the user will give the Secret again to the peer that have a capacity of regenerate the member account.

Cheers
There is no way to enforce this solution in the context of ERC2429.
p.s - gist

Author: axe
Date: 2020-01-23T11:16:29.515Z

This solution was dropped in favour a more capable solution of privacy.
Title: ERC_draft__Password_recovery_for_Account_Abstracti
Category: Web

Author: bui-duc-huy
Date: 2023-06-22T02:45:08.565Z

Password recovery for Account Abstraction Wallet
This topic proposes a new approach to password recovery for Account Abstraction Wallets, utilizing ZK-SNARKs (Zero-Knowledge Succinct Non-Interactive Arguments of Knowledge).
The central idea behind this proposal is to store the hash(password, nonce) on the contract wallet. In the event that a user loses their private key, which controls the contract wallet, they can employ their password to generate a zk-proof. This proof serves to verify that the user knows the password and requests a change of the private key. The confirmation process for this change will take approximately 3 days or more. Once confirmed, the contract wallet will update the hash(password, nonce + 1).
The zk-proof will contain public fields, including the newHash field. This field represents the updated hash value resulting from the password change process.
By utilizing ZK-SNARKs, the password recovery mechanism ensures that the user’s privacy is maintained. The proof only discloses the necessary information to verify the password and update the private key, without revealing any sensitive details about the password itself. This enhances the overall security of the Account Abstraction Wallet system.
In addition to ZK-SNARKs. The extended confirmation period of 3 days or more serves as a safeguard against unauthorized access attempts. It adds an extra layer of protection by introducing a time-based delay, allowing users to regain control of their wallet while mitigating the risk of malicious actors attempting to exploit the recovery process.
Implementing this password recovery mechanism on the contract wallet enhances the user experience by providing an alternative solution to regain access to their wallet in case of a lost private key. It offers a robust and secure approach that balances convenience and privacy, maintaining the integrity of the Account Abstraction Wallet system

Author: microbecode
Date: 2023-08-23T07:39:04.680Z

Hi here
I think this is an interesting approach to use ZK with AA. It’s a combination I’ve never even considered.
What’s the benefit compared to, for example, public key cryptography? Something like:

This would not be related to wallet/AA keys: a new set of private/public keys
contract has your public key
to make changes in the AA configuration, you sign some message with your private key. You send the signed message to AA contract with the plaintext message, and it verifies the data with the public key

Author: bui-duc-huy
Date: 2023-08-26T01:56:56.343Z

Hi, I found a solution to solve my issue above by using current ETH signature/address scheme, We won’t need to build an custom a zk-SNARKs schema, Check it out here: Password recovery for Account Abstraction Wallet - Applications - Ethereum Research
Title: We_need_more_support_for_ERC_681_
Category: Web

Author: ligi
Date: 2018-07-30T09:05:44.573Z

Alarmed by this tweet: https://twitter.com/Mesqueeb/status/1023714054492147712 I checked some wallets for ERC-681 support. Unfortunately it does not yet look as good as I hoped (https://twitter.com/wallethapp/status/1023856148041134080). Would be great to get more support for it. Also please test with wallets you know - would be great to get more data-points on this.

Author: boris
Date: 2018-07-30T14:12:35.639Z

For reference, ERC 681:



ERC-681: Representing various transactions as URLs

A standard way of representing various transactions, especially payment requests in Ether and ERC20 tokens as URLs.


Maybe a Wiki Page with wallets that support it?

Author: ligi
Date: 2018-07-30T14:21:50.083Z

boris:

Maybe a Wiki Page with wallets that support it?


Yes - I am working on this. But realized fast that this will be hell to edit in a table of github wiki page. Will make a extra repository that creates this table from json files.
The matrix should not only contain support of ERC-681 - but more ERCs and I also want to split ERC functions (e.g. ERC-681 value payload detection, ERC-681 function detection support, … )

Author: ligi
Date: 2018-08-02T08:24:54.108Z

More reasons why we need more support: https://github.com/walleth/walleth/issues/266
anyone has contacts to developers at BRD wallet or jaxx?

Author: ligi
Date: 2018-08-03T13:34:44.982Z

good news - jaxx answered on twitter that they will care for it. Trust mentioned in a github issue they will care for it. So I think ondly this BRD wallet is missing …

Author: ligi
Date: 2018-08-08T14:09:39.886Z

Just tested with enjin which is also quite large. Unfortunately they are also going off-standard - their ERC-681 looks like this:
ethereum:0x2E9F06153Ce4bf5cCE30bf18C1BA1899B50A18Ea?token=ETH
dropped them a mail and invited them to the ring - perhaps it would be good if more people write mails like this. They might ignore a single mail - but they cannot ignore us all 
support@enjin.com

Author: goranjovic
Date: 2018-10-31T16:08:18.901Z

Speaking for Status here. We only have a partial support for eip-681 or in other words, we don’t quite support it at the moment but definitely intend to and have it on our roadmap.
So, to avoid any confusion, we’ll definitely be adding support for this.
Title: What_happens_to_wallets_when_we_die_
Category: Web

Author: web3warren
Date: 2022-03-16T08:51:56.868Z

A secure beneficiary feature which transfers access to a wallet from its current passphrase to a new passphrase after a custom period of wallet inactivity, likely 1-5 years. This feature may be customized or deactivated by accessing the wallet with the owner’s original passphrase at any time prior to exceeding their chosen inactivity limit.
This feature allows the owner security and peace of mind by never needing to share their current passphrase with anyone. The replacement passphrase is presented upon activation of the beneficiary feature so it can be shared with someone or stored elsewhere without fear of the owner’s wallet being compromised while they’re still using it.
Put simply, the beneficiary feature is a passphrase reset activated upon wallet inactivity. Since the passphrase changes to a predetermined passphrase there’s no need to transfer the contents to a different wallet and pay gas/fees. No longer will wallets go lost and unopened when folks die! I’ll be able to leave my NFT collection to my family without concern. 
Feel free to follow me on Twitter @ web3warren

Author: high_byte
Date: 2022-05-22T21:04:29.114Z

that’s one use of social recovery. of course this will require smart wallets.

Author: SoundMoney
Date: 2022-09-03T19:29:24.199Z

This is possible today without any changes to Ethereum - I just don’t know of any solutions with a good UX.
On a technical level, you could do the following:

Code a smart contract that holds and controls your Ethereum assets (ETH, ERC20s, ERC721s, …)
The smart contract has two roles, admin role and lawyer role
Admin is you. You don’t share this key with anyone. As long as you’re alive, you can control all the assets in the smart contract without limitations.
There is a time-decay lock that enables the lawyer role to take control of the assets, but only after time T
Admin can always extend T

In practice, you can set T to a year in the future, and as long as you’re alive you extend T every year, by a year. If you die then your family has to wait for a maximum of one year to access the assets. Obviously you can also give the lawyer key to a family member directly.
Title: Is_defautt_Metamask_behavior_secure_
Category: Web

Author: kladkogex
Date: 2023-01-16T15:48:38.299Z

I found an interesting  thing about Metamask  recently
If you connect Metamask to a custom network node (say you have been using ETH mainnet and now you connect to a Goerllie node), Metamask  will immediately send all user’s public keys to this node by doing multiple eth_getBalance() queries , essentially deanonymizing all user keys and funds stored in Metamask on the Eth Mainnet
So if the user has 1000 keys in her wallet, Metamask will send all the keys to the node, the first time you connect to the network essentially fully deanomizing the user.
I wonder if wallets should behave like this.

Author: xinbenlv
Date: 2023-01-16T18:44:51.018Z

That’s interesting. Love to join the conversation
Topic-wise, this seems to better fit in the MetaMask forum.
Product feature wise, it seems it’s better MetaMask ask user to confirm they trust the Custom Node they are connecting to. But this will be hard.
Title: Https___www_cryptoinsiderreview_com_article_612187
Category: Web

Author: Kapu
Date: 2023-01-20T02:14:39.442Z

SIMGap
https://www.cryptoinsiderreview.com/article/612187101-taisys-introduces-the-smallest-hardware-wallet-in-the-world-for-crypto
Title: Earn_USD10_worth_of_ETH_in_a_paid_survey_for_Ether
Category: Web

Author: elishatorus
Date: 2021-10-22T00:29:53.791Z

Hello fellow developers! We’re conducting a paid survey and would remunerate you USD10 worth of ETH for your time and honest opinion: Survey
Title: Wallet_relevant_sessions_at_35c3
Category: Web

Author: ligi
Date: 2018-12-18T19:08:12.755Z

Hey - hope to see some members of the wallet ring at 35c3! Here some sessions that might be interesting to wallet devs:
Lecture: wallet.fail
Hacking the most popular cryptocurrency hardware wallets
https://fahrplan.events.ccc.de/congress/2018/Fahrplan/events/9563.html
Lecture: Wallet Security
How (not) to protect private keys
https://fahrplan.events.ccc.de/congress/2018/Fahrplan/events/9492.html
Lecture: A Blockchain Picture Book
Blockchain origins and related buzzwords, described in pictures.
https://fahrplan.events.ccc.de/congress/2018/Fahrplan/events/9573.html
Session: Ethereum Magicians gathering
https://events.ccc.de/congress/2018/wiki/index.php/Session:Ethereum_Magicians_gathering

Author: ligi
Date: 2018-12-21T00:30:16.301Z

One more interesting session (yes keys on smart-cards will be a thing in 2019 - https://github.com/status-im/status-keycard):
https://fahrplan.events.ccc.de/congress/2018/Fahrplan/events/9346.html
cc @bitgamma

Author: Tbaut
Date: 2019-01-04T09:23:27.411Z

Thanks for that, all the talk are viewable and downloadable here https://media.ccc.de/b/congress/2018

Author: esaulpaugh
Date: 2019-01-04T09:35:54.467Z

I have an idea about using iterated hashing to mitigate password-protected wallet owners’ vulnerability to coercion:
Time-Lock ASICs for Password-protected Wallets: https://github.com/esaulpaugh/scratchpaper/blob/master/Crypto-Time-Lock
Instead of memorizing your wallet password, memorize your wallet password’s seed and hash it repeatedly to generate the wallet password. Seed (i.e. master password) “Jeb!2064” might produce derived password “bdrvpUu8N8xN3s7xi22jM” after 80 billion iterations.
By the time the attacker knows you’ve given him a fake (master) password, many hours or days will have elapsed, making attacks expensive/risky.
Title: Introducing_Myself___Experience_Designer
Category: Web

Author: Nik
Date: 2018-07-01T09:29:40.165Z

Hi
I’m Nik
Just introducing myself and saying Hi.
I was introduced to the fellowship yesterday at DAPP Conf in Prague. I’m long time UX / experience designer.
linkedin.com/in/nbpage/

Author: 0rand
Date: 2018-07-01T11:36:14.241Z

Hi Nik! Welcome!
Alex
Title: Smart_Contract_Wallets___Migration___Interoperabil
Category: Web

Author: c-o-l-o-r
Date: 2018-11-13T09:32:18.353Z

I have been thinking a lot about what the future of wallets look like and how we streamline the on-boarding of new users and I’ve come up with a few thoughts. I would like to start a dialogue with everyone and see how others in the space see the future. I also feel like there is a lot of fragmented and duplicate work is going on right now and it would be great to consolidate our efforts a bit.
I believe smart contract wallets will eventually account for the majority of wallets in use. I think Universal Login is a great example of how we’ll use smart contract wallets in the future. I foresee smart contract wallets becoming what we know today as our bank account and it will be ubiquitous with storing money.
We’re a long way from that and I think there are a couple core issues that need to be overcome to reach this.
First off, on-boarding needs to be easy. It is unrealistic to get new users into dapps and expect them to signup for the dapp and a wallet at this time. The dapp should be able to create a contract wallet for their user and store an ephemeral key on their device. Once the user decides its time to upgrade to a real wallet, that contract should either be able to plug directly into a real wallet interface or it should be able to be migrated to a more fully featured contract like Gnosis Safe.
All wallet contracts should implement a core set of features. Every dapp on the planet should be able to interact with any smart contract wallet, regardless of what extra modules / feature are included. In this same vein, smart contract wallets should be mobile. If one day the wallet provider I use does something I don’t like, I should be able to pack up my contract and move everything over to a different provider with little friction. I imagine it like being able to move all your money / personal info / history from one bank to another at the press of a button.
In order to address the issues I’ve raised, it seems like there are two avenues we can take: migrations & interoperability. I’d argue we need both.
Interoperability (between dapps and wallet UIs) is the ideal route to take, because it doesn’t rely on issuing a new contract wallet. However, I think that if this is the only route we explore we will end up in a corner by ourselves with a bunch of modules. I believe that also setting a standard for migrating between contract wallets early will avoid this and allow development to continue and improve the experience without restrictions.
This was a bit of a brain dump, I look forward to hearing what some others in this space are thinking! Please direct me to any existing EIPs or discussions that may be relevant.

Author: c-o-l-o-r
Date: 2018-11-13T15:31:47.086Z

Can you elaborate on the actor/asset model? And who is publishing this article?

Author: bumblefudge
Date: 2025-02-20T13:34:53.489Z

heh, did this get pulled out of another thread or something? I can’t see what Antoine Herzog post this is responding to
Title: WalletConnect_WCIP_2
Category: Web

Author: ligi
Date: 2019-05-13T16:12:27.868Z

We need more eye-balls on WCIP-2:
https://github.com/WalletConnect/WCIPs/issues/2
I strongly feel it would be a mistake to adopt this change. But we need more eyes on this.
Title: _Survey__Help_wallets_improve__What_are_you_curren
Category: Web

Author: deltajuliet
Date: 2018-10-24T18:10:42.917Z

Curious to find out what the group is using for wallets, we’re looking to improve on existing models.
Appreciate any feedback anyone has, would love to hear from the community what is missing in the apps that are in the market right now.
I’ve been getting the biggest mix of reactions to this question. From ‘the market is saturated’ to ‘no one uses mobile ETH wallets’. Personally the only thing that comes up in my ads these days is more ads for wallets. 
Survey is here: https://totle.typeform.com/to/gdPFh7

Author: boris
Date: 2018-10-25T07:07:38.940Z

Hello! Will you be sharing anonymized results from the survey?

Author: ligi
Date: 2018-10-26T10:07:42.434Z

I would be most interested in the results - please share them in the wallet ring!!

Author: deltajuliet
Date: 2018-11-04T01:22:04.887Z

Definitely will, working diligently now to make sure we get a larger snapshot to make it worthwhile for you guys (and my team!)

Author: Tbaut
Date: 2018-11-20T14:13:44.403Z

@deltajuliet did you get the chance to consolidate the results?

Author: deltajuliet
Date: 2018-11-20T17:14:40.231Z

Yes @Tbaut! Apologies for the delay. We’ve been super busy getting results and iterating. 
A high level overview is here: https://totle.typeform.com/report/gdPFh7/LWCTe4pXnsiyoZUv
And more detailed comments from participants is here: Mobile Eth Survey - Google Drive
Please send any feedback you have, and of course, we’d love for this survey to be shared for even more results, to your groups. I am only able to add 2 links to posts so I’ll post the survey link in the next response.

Author: deltajuliet
Date: 2018-11-20T17:17:50.162Z

Looks like my post was flagged as spam. I’m unable to post the links here. Working on getting that flag removed!

Author: Tbaut
Date: 2018-11-20T17:31:00.008Z

Probably a bot that doesn’t like too many links. Thank you so much for the results.

Author: deltajuliet
Date: 2018-11-26T15:58:38.901Z

Happy to help @Tbaut. We have a working prototype for those who are interested in giving feedback. I can post here if interested.
Title: About_the_Web_category
Category: Web

Author: nicocsgy
Date: 2024-09-05T14:19:24.428Z

(Replace this first paragraph with a brief description of your new category. This guidance will appear in the category selection area, so try to keep it below 200 characters.)
Use the following paragraphs for a longer description, or to establish category guidelines or rules:


Why should people use this category? What is it for?


How exactly is this different than the other categories we already have?


What should topics in this category generally contain?


Do we need this category? Can we merge with another category, or subcategory?
Title: Request_for_Proposals___Sign_In_with_Ethereum__Spe
Category: Web

Author: jpitts
Date: 2021-07-20T18:38:20.654Z

The Ethereum Foundation (EF) and True Names LTD (ENS) would like to announce a Request for Proposals (RFP) for the creation of a Sign-In with Ethereum specification, a package using Oauth for easy implementation by web2 services, and a Javascript library for the user-facing part of sign-in.
…
Proposals must be submitted before July 30th, 2021 at 5pm PST

The RFP: Sign-in with Ethereum RFP - HackMD
The Tweet:
https://twitter.com/ensdomains/status/1414618006710329347

Author: NhlanhlaHasane
Date: 2021-07-24T05:49:35.184Z

I’ve had a thought about how amazing it is since the ENS is linked to all my wallet addresses why not extend it to Decentralized Email Providers like https://disroot.org and
Title: Crypto_Adoption__UX_Research
Category: Web

Author: Nik
Date: 2018-08-29T12:20:08.524Z

Hi
I’m getting more and more into research & experimentation into bringing about mass adoption for crypto. I’ve started a site (ugly - please don’t judge me by the wordpress   ) to see if I can find any interested partners.
solutioncells.org
I don’t want to accept the “common wisdom” that no one wants to spend crypto. I believe they haven’t met the right motivation to do so.

Author: boris
Date: 2018-09-01T19:41:35.800Z

Hey Clay – promotion of particular projects is discouraged in this forum. You’re totally welcome to click on Nik’s profile and PM (private message) him (or anyone else).
Here’s a link to my profile if you’d like to PM and discuss further: https://ethereum-magicians.org/u/boris

Author: jpitts
Date: 2018-09-02T22:19:52.140Z

@Nik, really glad that you are looking into UXR for crypto adoption. I was just in a conversation the other day with an engineer lead who did not fully understand or appreciate the difficulties of new users to crypto.
A key question is: what are the basic needs of users of smart contracts and dapps? What properties of public blockchains are attractive to them (hopefully not just the rising asset prices)? How can the first-time user’s experience be made better while preserving those sought-after properties?

Author: Nik
Date: 2018-09-03T06:22:55.534Z

Hi @jpitts
As an old UXER (first) and techno enthusiast after… I turn that question around sorta…
What emotions, motivation & drives can I create a something fun and/or useful around?
What tech (or skills my company has) can I use to do the above?
Those who don’t know a new tech don’t have ANY basic needs/wants/ etc pertaining to them. They have lived their whole lives perfectly well without.  It’s up to us to figure out what might be cool.
Also - I’d drop “hose sought-after properties” entirely. I know a lot of blockchain / crypto people hate me for it - but 99.[9 to 18 decimal places]% of non-crypto geeks people don’t give a hoot about the cool stuff we see - and probably are scared of it if they knew. If we want their attention, money, eyeball & brain time… the only relevant UX question is about their emotions.

Author: Alex
Date: 2018-09-05T03:08:28.350Z

I wrote a recap from my research for 0xProject: https://medium.com/wicketh/decentralized-exchanges-for-humans-adced960aeca