Josh Quintal

Hi @sbrichards, we've made some changes to the `transactionStack` which will probably help here. [See the docs here](https://truffleframework.com/docs/drizzle/reference/drizzle-state#-code-transactionstack-code-array-), but the TL;DR is that a temporary ID will be pushed to...

@gconaty To clarify that I'm understanding your correct: you're able to stop the polling with `yield cancelled()`; the issue is restarting the polling afterwards?

Tagged for 2.0 because polling will be fully supplanted by subscriptions, but we will probably want some more manual control over the subscription status.

This occurs because account fetching triggers after `web3` is connected. We could separate these to allow greater control over when the popup appears. @hackingbeauty Can you describe or link to...

@mi-kas Not currently, but you can use the `web3` object exposed by Drizzle with `drizzle.web3`. We are discussing this feature.

Thinking through this it seems like we need a middleware modification to track network changes and update contracts accordingly. We may also want to consider a unified source of truth...

For optimal UX we could consider a read-only connection as the default so the dApp UI will populate, assuming it's only calls. Take [Ethlance](https://ethlance.com/#/find/work) for example: ideally users could view...

LGTM @jklepatch thank you! Potential method names: `connectWallet()`, `requestWallet()`.

Hi @makoto this is definitely something we want to support. Can you give us more insight into how you're using the tx history? Thanks!

@DSandman Are there any errors in the console? When clicking sign up does it redirect anywhere? Last question: Are you using MetaMask in Chrome? Thanks!