Why is the new Tx fee causing so much delay in sending/receiving DGB?

[ZuneTracks]

Greetings Digibyte team!

Despite updating all of my wallets to 8.22.2, it seems like this new fee is still causing massive delays in transaction speed. Just as an example, I sent 85 DGB from one 8.22.2 wallet to my cold storage wallet, and after nearly 4 hours, it's still sitting in mempool as unconfirmed. I have a Tx id, however the blockchain does not see it.

The speed of the DGB network is one of my favorite features, but it feels like we've cut it off at the knees with the new fee. What can be done about it? Why was the new fee implemented? I'm asking sincerely. As scrypt miner, I'm generally curious about this.

I very much appreciate the dedication of this team to this technology that I love and use every day!!! Thank you all!

[ycagel]

Can you provide transaction IDs? Sounds like a localized issue.

[ZuneTracks]

2141f7005e3b68d88c308541719542336ff68c7ef48508f07efa7a82f4bdf29d

[ycagel]

Have you tried setting the fallback fee to .01/kb?

[ZuneTracks]

I did not. I let it auto calculate whenever I send my DGB. If it matters, the Tx fee is .06290000 DGB at a Tx size of 629 bytes.

[ycagel]

Are you able to create a PR regarding this and document as much as possible?

[ZuneTracks]

absolutely! I'm AFK for most of the day but will get a pull request submitted ASAP.

As of this morning my Tx is still sitting in mempool unconfirmed.

[ycagel]

Please provide what machine, OS, build, logs, and the mechanism to create the transaction, etc.

[ZuneTracks]

@ycagel every time I try to submit a new pull request to the digibyte repo, it tells me that the repo has been archived as of may 2024. Am I missing the proper link? I'm going here to submit the pull request:
https://github.com/DigiByte-Core/digibyte/pulls

[ycagel]

Click the button on the left and choose the DigiByte-core/digibyte repo and then on the right your repo.

[ZuneTracks]

I'm not sure what I'm doing wrong but I'm still getting this page that says the repo has been archived.

I'm going here: https://github.com/DigiByte-Core/digibyte/pulls and click on new Pull Request and its' taking me to the page in the screenshot above.

Edit: please bear with me. I've never used GitHub before, so this is all new to me.

[saltedlolly]

@ZuneTracks That is the old repo that has been archived. Development was moved to the new org several years ago. You need this one: https://github.com/DigiByte-Core/DigiByte

(I agree it is confusing!)

[ZuneTracks]

That's what I don't understand. When I go to the page you linked to and I click on New Pull Request, it takes me to the page saying it's been archived.

[ZuneTracks]

For the record my Tx is still sitting unconfirmed in the mempool. My apologies for not getting a pull request submitted, but every time I go to https://github.com/DigiByte-Core/digibyte/ and click on New Pull Request, it takes me to the archived page. I've changed my base repository and head repository to both point to digibyte-core but the same thing happens and it takes me to the archived page.

[ZuneTracks]

@ycagel I finally figured out how to get off that archived pull request. I changed "base" to v8.22.1 and "compare" to develop for the repos, but now it tells me I must be a collaborator to submit a pull request. I couldn't find v8.22.2 as an option for "base"...despite that being where my issue is.

[ZuneTracks]

@ycagel I submitted a bug fix, since I can't do a Pull Request. I hope that is ok. My apologies if I didn't do this properly.

#310