[ANN][Flux] ZelCore - FLUX - First Decentralized Computational Network - page 25.

dtr

newbie

Activity: 164

Merit: 0

Quote from: trial123 on August 22, 2018, 11:41:19 AM

the best practice to unshield funds with any of these privacy coins is to send to a t-address in the same wallet as the z-address you are sending from.

No, that didn't work for me, got the same error. Reindex also didn't help.
Anyway, I got some luck to restore original wallet from backup and with it finally managed to withdraw all coins from z-addresses.

I think I will just avoid using z-addresses for keeping funds with all my zk coins.

trial123

newbie

Activity: 140

Merit: 0

I know Discord isnt everyone's favorite place, but for real-time support of ZelTreZ or ZelCash project, its the best place. Here is an invite link for anyone interested

https://discord.gg/svDHPud

trial123

newbie

Activity: 140

Merit: 0

Quote from: dtr on August 22, 2018, 09:36:30 AM

Quote from: trial123 on August 20, 2018, 10:25:37 AM

since they are not full node wallets, they create lightweight addresses, and you cant import priv keys for your full node addresses. You would send the coin from your full node to your lightweight address.

Ok. Now I'm trying to send coins from my full node z-address to light t-address.
I got error "witness for note commitment is null" and transaction is not going out.

I think this is a known issue with the ZCash codebase. Here is a support ticket that explains the issue and some potential workarounds. In general, the best practice to unshield funds with any of these privacy coins is to send to a t-address in the same wallet as the z-address you are sending from.

https://github.com/zcash/zcash/issues/2524

dtr

newbie

Activity: 164

Merit: 0

Quote from: trial123 on August 20, 2018, 10:25:37 AM

since they are not full node wallets, they create lightweight addresses, and you cant import priv keys for your full node addresses. You would send the coin from your full node to your lightweight address.

Ok. Now I'm trying to send coins from my full node z-address to light t-address.
I got error "witness for note commitment is null" and transaction is not going out.

trial123

newbie

Activity: 140

Merit: 0

Here is the link for the Zel live public meeting - August 21st. Its around 8 minutes long so please watch as time permits and get caught up on the latest Zel happenings including CCC.
https://youtu.be/0H-OGe-2_BU

trial123

newbie

Activity: 140

Merit: 0

Quote from: dtr on August 20, 2018, 05:29:23 AM

Quote from: trial123 on August 16, 2018, 12:03:59 PM

If you want, to get around the issue, you can also move to a lightweight wallet like ZelTreZ or Copay that doesnt require the daemon and full blockchain copy, just access to the internet.

Ok, I'd like to try a light wallet - how can I import my private keys to any of them? Didn't find that option.

since they are not full node wallets, they create lightweight addresses, and you cant import priv keys for your full node addresses. You would send the coin from your full node to your lightweight address.

dtr

newbie

Activity: 164

Merit: 0

Quote from: trial123 on August 16, 2018, 12:03:59 PM

If you want, to get around the issue, you can also move to a lightweight wallet like ZelTreZ or Copay that doesnt require the daemon and full blockchain copy, just access to the internet.

Ok, I'd like to try a light wallet - how can I import my private keys to any of them? Didn't find that option.

jacko0088

hero member

Activity: 1148

Merit: 562

Blockchain Core Dev

Zel was added on EquiGems mining pool!

https://equigems.online/getting_started

Code:

stratum+tcp://equigems.online:[COIN-PORT] -u [YOUR-PAYOUT-ADDRESS] -p ANYTHING

trial123

newbie

Activity: 140

Merit: 0

ZelTreZ released update 1.0.7.
The following features, assets, and bug fixes are now integrated and live

- Following coins added: Tether (USDT), Bitcoin Private (BTCP), Kyber (KNC), Enigma (ENG), TenX (PAY), Substratum (SUB).
- A confirmation dialog is now showing when clicking full node button to prevent accidental clicks.
- Payment notes are now accessible in light mode in all coins except ethereum and tokens. You can receive and send coins with a short note attached to a transaction.
- Kyber - decentralized exchange for ethereum and its tokens added.
- New Ravencoin fullnode binaries in order to support upcoming hardfork.

Bug Fixes

- Sometimes it was possible that Zcoin showed wrong balance as some coins are staying in both states - confirmed and unconfirmed. User will now see only balance that is fully onfirmed by the network
- When having a lot of activated ethereum tokens, the initial proccess of obtaining transactions was failing for a few tokens.
- Changelly status after a shift was not working properly.
- When firstly installing a full node coin a stuck at verification of the files may occur.

mySmile28

jr. member

Activity: 98

Merit: 1

Quote from: trial123 on August 16, 2018, 12:03:59 PM

Quote from: dtr on August 16, 2018, 07:33:55 AM

Quote from: trial123 on August 15, 2018, 09:46:25 AM

If you are on Windows, theres a chance that Windows Defender is stopping zelcashd from running automatically. You should not have to start the daemon manually unless some AV software is actively stopping the process.

Tried to disable defender. Didn't help, daemon won't start automatically.
No other AV is present.

Something on the computer is blocking the daemon from automatically launching. It could also be Windows Firewall. The daemon will start if allowed.

If you want, to get around the issue, you can also move to a lightweight wallet like ZelTreZ or Copay that doesnt require the daemon and full blockchain copy, just access to the internet.

ZelTreZ will be best way)

trial123

newbie

Activity: 140

Merit: 0

Quote from: dtr on August 16, 2018, 07:33:55 AM

Quote from: trial123 on August 15, 2018, 09:46:25 AM

If you are on Windows, theres a chance that Windows Defender is stopping zelcashd from running automatically. You should not have to start the daemon manually unless some AV software is actively stopping the process.

Tried to disable defender. Didn't help, daemon won't start automatically.
No other AV is present.

Something on the computer is blocking the daemon from automatically launching. It could also be Windows Firewall. The daemon will start if allowed.

If you want, to get around the issue, you can also move to a lightweight wallet like ZelTreZ or Copay that doesnt require the daemon and full blockchain copy, just access to the internet.

longestday3030

member

Activity: 132

Merit: 10

Good to see Zelcash developments being shared consistently in Twitter. I'm seeing Zelcash more and more lately in social media. Still holding to my future masternode coins. In the past couple of days when BTC and other altcoins were being hammered, only Zelcash was going higher. Looks like bright days are ahead.

dtr

newbie

Activity: 164

Merit: 0

Quote from: trial123 on August 15, 2018, 09:46:25 AM

If you are on Windows, theres a chance that Windows Defender is stopping zelcashd from running automatically. You should not have to start the daemon manually unless some AV software is actively stopping the process.

Tried to disable defender. Didn't help, daemon won't start automatically.
No other AV is present.

trial123

newbie

Activity: 140

Merit: 0

Quote from: dtr on August 15, 2018, 07:28:42 AM

I run zelcashd.exe manually and now finally wallet is starting.
That's kinda upsetting for a gui wallet.

If you are on Windows, theres a chance that Windows Defender is stopping zelcashd from running automatically. You should not have to start the daemon manually unless some AV software is actively stopping the process.

dtr

newbie

Activity: 164

Merit: 0

I run zelcashd.exe manually and now finally wallet is starting.
That's kinda upsetting for a gui wallet.

Cora_ED

jr. member

Activity: 140

Merit: 1

Now in such a difficult time, I think any news it will be good to influence the community. The team Zelcash often need to give the news that they actually do.

dtr

newbie

Activity: 164

Merit: 0

Quote from: dtr on August 14, 2018, 04:26:22 PM

As I wrote - I already did this. Nothing.
After wallet start there appears only zelcash.conf in the folder. No debug.log,
no blocks subfolder, nothing.

In the background I can see zelcash-cli.exe trying to start and immediately closing.

The old wallet was working without a problem.

dtr

newbie

Activity: 164

Merit: 0

Quote from: trial123 on August 14, 2018, 03:28:35 PM

Quote from: dtr on August 14, 2018, 09:21:53 AM

Just tried to update from old 0.2 swing wallet to new 4.0
New one is not starting: "could not connect to server. EOF reached (code 1)"
Tried to delete data folder - no luck, got same error.

Deleting everything but the wallet.dat file in the Zelcash data folder under \AppData\ should do the trick.

As I wrote - I already did this. Nothing.
After wallet start there appears only zelcash.conf in the folder. No debug.log,
no blocks subfolder, nothing.

Quote

You can add these nodes to your zelcash.conf file to "jump start" the sync of the correct chain.
addnode=node.zel.cash
addnode=45.63.86.148
addnode=45.76.128.62
addnode=45.76.186.252
addnode=158.140.144.78

That did nothing.

trial123

newbie

Activity: 140

Merit: 0

Quote from: dtr on August 14, 2018, 09:21:53 AM

Just tried to update from old 0.2 swing wallet to new 4.0
New one is not starting: "could not connect to server. EOF reached (code 1)"
Tried to delete data folder - no luck, got same error.

Deleting everything but the wallet.dat file in the Zelcash data folder under \AppData\ should do the trick.

You can add these nodes to your zelcash.conf file to "jump start" the sync of the correct chain.
addnode=node.zel.cash
addnode=45.63.86.148
addnode=45.76.128.62
addnode=45.76.186.252
addnode=158.140.144.78

dtr

newbie

Activity: 164

Merit: 0

Just tried to update from old 0.2 swing wallet to new 4.0
New one is not starting: "could not connect to server. EOF reached (code 1)"
Tried to delete data folder - no luck, got same error.

Topic: [ANN][Flux] ZelCore - FLUX - First Decentralized Computational Network - page 25. (Read 62346 times)