Development resources at your finger tips
Build with the coolest Web3 projects
Recurring funding for Open Source
Learn about Web3 & earn rewards
Show appreciation for each other
Meet fellow developers, designers, futurists and more. Collaborate and BUIDL awesome projects together.
Discover great web3 organizations, work on meaningful projects and build relationships with like minded people. Browse Tribes
Meet the top hunters and contributors from our community.
A little over three months ago, we announced the beginning of KERNEL. An experiment in building a highly curated community of talented builders in We…
GoodDollar is live and over 20,000 users have created wallets from every corner of the globe. Are you interested to learn how we plan to use smart co…
Gitcoin is GDPR compliant. Learn more in
Gitcoin's Terms & Conditions.
Check out the Issue Explorer
Looking to fund some work? You can submit a new Funded Issue here.
_Before filing a new issue, please **provide the following information**._
> I'm running:
> - **Which Parity version?**:
> - **Which operating system?**:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.4 LTS
> - **How installed?**: via installer / homebrew / binaries / from source
compiled rustc (1.25.dev) --> compiled cargo (0.26) --> compiled parity (git:e30839e85ff74cd5eb087ef19a48d70afd1fd285)
> - **Are you fully synchronized?**:
Yes. Completely new setup using `--config dev`
> - **Which network are you connected to?**: ethereum / ropsten / kovan / ...
built-in dev config
> - **Did you try to restart the node?**: no / yes
n/a. The problem appears immediately after start
_Your issue description goes here below. Try to include **actual** vs. **expected behavior** and **steps to reproduce** the issue._
**expected behavior:** Export state to file with `parity export state foo.txt`.
**actual behavior:** I re-started the node with `--fat-db` on and still received the error.
parity --config dev --fat-db on
Starting with no db at all
~$ find .
Even with `--fat-db on` from the beginning, in another terminal I get:
~$ parity export state foo.txt
This command requires Parity to be synced with --fat-db on.
I notice the word "synced", is that something I need to do in addition to running with `--fat-db on` from an _empty_ database?