-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
can't send my DGB #1
Comments
means your trying to send a tx with smaller fee then the server allows. most insight servers require at least 20sat/byte fee. |
Thanks. and you know how to fix it. please tell me. |
where did you get the error? to fix increase fee paid. |
my wallet Guarda come with mining DGB with him, I was not able to send the DGB was a mistake http://skrinshoter.ru/v/290419/XvoX0gcX. then I imported the key on magnumwallet was this error http://skrinshoter.ru/s/030519/WIsgPYve. tried to send via DigiSweep the same did not work( tech support for 7 days could not solve the problem. |
If you are mining to a wallet I recently released an android app that will
automatically fix the wallet from time to time. Works by sending funds
from mining address in lumps to your next change address when ever a lot of
transactions have accrued.
https://play.google.com/store/apps/details?id=rocks.digibyte.digibyte_wallet_fixer
try it out and let me know what you think.
…On Sun, May 5, 2019, 9:23 AM 3dima3, ***@***.***> wrote:
my wallet Guarda come with mining DGB with him, I was not able to send the
DGB was a mistake http://skrinshoter.ru/v/290419/XvoX0gcX. then I
imported the key on magnumwallet was this error
http://skrinshoter.ru/s/030519/WIsgPYve. tried to send via DigiSweep the
same did not work( tech support for 7 days could not solve the problem.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADRERA52BEAU573KXOZEQTDPT3UUFANCNFSM4HKZQWBA>
.
|
can't import key( |
your going to need to be a lot more descriptive then that. is that an error you got. what where you doing at the time in what program... |
failed to import the key into your digibyte Wallet Fixer. I've downloaded the QR code and press"send" and nothing happens |
I meant "check"//not "send" |
So in the add address screen after you set everything up you tried scanning
the private key in and it failed?
…On Sun, May 5, 2019, 2:31 PM 3dima3, ***@***.***> wrote:
I meant "check"//not "send"
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADRERA2NGAZAWOOAXPKZHU3PT4Y2BANCNFSM4HKZQWBA>
.
|
I key scanned it appeared in the line I press "check" but nothing happens |
you need to give me a lot more info then this. find me on telegram
t.me/mctrivia and send me a screen shot.
…On Sun, May 5, 2019, 7:45 PM 3dima3, ***@***.***> wrote:
I key scanned it appeared in the line I press "check" but nothing happens
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADRERAYAWN775MM2QWSLPO3PT55SLANCNFSM4HKZQWBA>
.
|
black out key if in image
On Sun, May 5, 2019, 7:50 PM Matthew Cornelisse, <
[email protected]> wrote:
… you need to give me a lot more info then this. find me on telegram
t.me/mctrivia and send me a screen shot.
On Sun, May 5, 2019, 7:45 PM 3dima3, ***@***.***> wrote:
> I key scanned it appeared in the line I press "check" but nothing happens
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#1 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ADRERAYAWN775MM2QWSLPO3PT55SLANCNFSM4HKZQWBA>
> .
>
|
please tell me. can't send my DGB.
{ "error": {}, "data": "Transaction rejected by network (code -26). Reason: min relay fee not met, 10000 < 73793 (code 66)" }
The text was updated successfully, but these errors were encountered: