Skip to content
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

Unable to create an alias with aliasnew #204

Closed
johnp1954 opened this issue May 24, 2018 · 7 comments
Closed

Unable to create an alias with aliasnew #204

johnp1954 opened this issue May 24, 2018 · 7 comments

Comments

@johnp1954
Copy link

johnp1954 commented May 24, 2018

I have this issue , no matter what i tried i could not get it to confirm the first TX, discussed this with @willyk with no solution. The only way I could get Alias creation to work was to create a new wallet. I am hoping that it works when we get BM3 as all my MN coins are in the wallet that does not work. So to summarise, I have 3 wallets all on 3.0.4 2 will allow Alias creation (and this is just Aliasnew no funding etc) 1 (My Main wallet) will not allow it. I have tried clearing syscoincore,rescan,reindex dumpwallet none of these worked. This wallet was the one i imported from Sys 2 via 3.0.0 and salvagewallet=1. It seems that i am not the only one having these issue now.

@oldominion
Copy link

I too have this issue. Same upgrade path.

@bstr156
Copy link
Member

bstr156 commented May 24, 2018

Same issue. First TX will not confirm. Running Syscoin Core version v3.0.2.0-dbe0afd for what it's worth. "Recover Transactions 1" seems to clear the stuck transactions. Syscointxfund was executed using an MN address with all mined transactions having > 101 confirmations, fully confirmed. Discussed with @doublesharp. No solution as of yet.

@bstr156
Copy link
Member

bstr156 commented May 24, 2018

Issue might be related to addresses generated in non-HD wallets. It appears we can create aliases fine as long as the TX funding address is recent, and the target address for the alias is recent or HD.

Two problem scenarios:

  1. When using an older address (generated shortly after the Syscoin 3 hard fork) to fund the alias TX, the first transaction is never confirmed.
  2. When using a newer address to fund the alias TX, and attempting to associate an alias with an older address, the first transaction confirms fine, but the second execution of syscoinsendrawtransaction produces an error. The following shows up in the log: "insufficient priority (18270 < 18540)" accompanied by "66: insufficient priority (code -1)" as the Console output.

@johnp1954
Copy link
Author

johnp1954 commented May 25, 2018

Ok so to summarise

  1. You cannot create an Alias in a wallet that was HD without creating a new HD address as the funding source.
  2. You cannot create an alias on an existing non HD address even with using a HD funding address.

@sidhujag
Copy link
Member

please try in 3.0.4.1

@doublesharp
Copy link

@doublesharp
Copy link

Closing as 3.0.4.1 confirmed to fix tx fees for alias creation with several users having issues with older versions.

sidhujag pushed a commit that referenced this issue Feb 22, 2021
…questsView tables column sizes

964885d qt: Save/restore recentRequestsView table column sizes (Hennadii Stepanov)
f5c8093 qt: Move recentRequestsView properties settings to constructor (Hennadii Stepanov)
9c5f4f2 qt: Save/restore TransactionView table column sizes (Hennadii Stepanov)
788205c qt: Move transactionView properties settings to constructor (Hennadii Stepanov)
ecdbaf7 qt, refactor: Drop intermediate assignment (Hennadii Stepanov)

Pull request description:

  Save/restore TransactionView and recentRequestsView tables column sizes.
  Sorting order is not saved/restored intentionally.

  Based on #204 (the first commit).

ACKs for top commit:
  jarolrod:
    ACK 964885d, tested on macOS 11.1 Qt 5.15.2
  Talkless:
    tACK 964885d, tested on Debian Sid, saving/restoring and resetting (with `-resetguisettings`) works as expected.

Tree-SHA512: c24e41bf4d95bb33dce16e9a0b952ffd0912e95f4d2a1bc5292fcf5a27100e70fea73433c4ff246d05b174fc23a7b6de1790a2e8b990a9089e4deca79a00dedc
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants