invalid utf-8 AccountAgeWitnessStore

[KodeToad]

Platform Manjaro Fresh install bisq-git 0.7.1.r5.ge0cbd7c62-1 Backup was created in a different location after adding National currency accounts. When posting a sell offer, this exception is generated. BTC is reserved and a fee is extracted but the offer is never posted. The trade is cancelled and BTC released but the fee is net returned.

Jul-18 05:02:33.349 [readFromResourcesThread] ERROR b.c.s.FileManager: Exception at proto read: Protocol message had invalid UTF-8. file:/home/dir/.local/share/Bisq/btc_mainnet/db/AccountAgeWitnessStore com.google.protobuf.InvalidProtocolBufferException: Protocol message had invalid UTF-8.
    at com.google.protobuf.InvalidProtocolBufferException.invalidUtf8(InvalidProtocolBufferException.java:148)
    at com.google.protobuf.CodedInputStream$StreamDecoder.readStringRequireUtf8(CodedInputStream.java:2329)
    at io.bisq.generated.protobuffer.PB$TradeStatistics2.<init>(PB.java)
    at io.bisq.generated.protobuffer.PB$TradeStatistics2.<init>(PB.java)
    at io.bisq.generated.protobuffer.PB$TradeStatistics2$1.parsePartialFrom(PB.java)
    at io.bisq.generated.protobuffer.PB$TradeStatistics2$1.parsePartialFrom(PB.java)
    at com.google.protobuf.CodedInputStream$StreamDecoder.readMessage(CodedInputStream.java:2399)
    at io.bisq.generated.protobuffer.PB$TradeStatistics2Store.<init>(PB.java)
    at io.bisq.generated.protobuffer.PB$TradeStatistics2Store.<init>(PB.java)
    at io.bisq.generated.protobuffer.PB$TradeStatistics2Store$1.parsePartialFrom(PB.java)
    at io.bisq.generated.protobuffer.PB$TradeStatistics2Store$1.parsePartialFrom(PB.java)
    at com.google.protobuf.CodedInputStream$StreamDecoder.readMessage(CodedInputStream.java:2399)
    at io.bisq.generated.protobuffer.PB$PersistableEnvelope.<init>(PB.java)
    at io.bisq.generated.protobuffer.PB$PersistableEnvelope.<init>(PB.java)
    at io.bisq.generated.protobuffer.PB$PersistableEnvelope$1.parsePartialFrom(PB.java)
    at io.bisq.generated.protobuffer.PB$PersistableEnvelope$1.parsePartialFrom(PB.java)
    at com.google.protobuf.AbstractParser.parsePartialFrom(AbstractParser.java:221)
    at com.google.protobuf.AbstractParser.parsePartialDelimitedFrom(AbstractParser.java:262)
    at com.google.protobuf.AbstractParser.parseDelimitedFrom(AbstractParser.java:275)
    at com.google.protobuf.AbstractParser.parseDelimitedFrom(AbstractParser.java:280)
    at com.google.protobuf.AbstractParser.parseDelimitedFrom(AbstractParser.java:49)
    at com.google.protobuf.GeneratedMessageV3.parseDelimitedWithIOException(GeneratedMessageV3.java:347)
    at io.bisq.generated.protobuffer.PB$PersistableEnvelope.parseDelimitedFrom(PB.java)
    at bisq.common.storage.FileManager.read(FileManager.java:125)
    at bisq.common.storage.Storage.getPersisted(Storage.java:152)
    at bisq.common.storage.Storage.initAndGetPersistedWithFileName(Storage.java:84)
    at bisq.network.p2p.storage.persistence.StoreService.readStore(StoreService.java:128)
    at bisq.network.p2p.storage.persistence.StoreService.readFromResources(StoreService.java:98)
    at bisq.network.p2p.storage.persistence.AppendOnlyDataStoreService.lambda$readFromResources$0(AppendOnlyDataStoreService.java:57)
    at java.util.ArrayList.forEach(ArrayList.java:1257)
    at bisq.network.p2p.storage.persistence.AppendOnlyDataStoreService.readFromResources(AppendOnlyDataStoreService.java:57)
    at bisq.network.p2p.storage.P2PDataStorage.readFromResources(P2PDataStorage.java:155)
    at bisq.core.app.SetupUtils.lambda$readFromResources$1(SetupUtils.java:98)
    at java.lang.Thread.run(Thread.java:748)

Jul-18 05:02:33.351 [readFromResourcesThread] ERROR b.c.s.Storage: We cannot read the persisted data. We make a backup and remove the inconsistent file. fileName=AccountAgeWitnessStore 
Jul-18 05:02:33.351 [readFromResourcesThread] ERROR b.c.s.Storage: Exception at proto read: Protocol message had invalid UTF-8. file:/home/dir/.local/share/Bisq/btc_mainnet/db/AccountAgeWitnessStore 
Jul-18 05:02:33.378 [readFromResourcesThread] INFO  b.c.a.SetupUtils: readFromResources took 5398 ms 
Jul-18 05:02:33.386 [JavaFX Application Thread] INFO  b.c.a.P2PNetworkSetup: init 

[ManfredKarrer]

Hm, never saw such an exception before. Might be that the protobuffer file got corrupted at storage. The AccountAgeWitnessStore will get recreated at restart and the worst thing possible is that your own account witness got deleted (dont think so). You can check at your payment account the age of the account. I can refund you for your lost offer fee, though it is usually very small amount (about 1 USD), but if you like ping me on slack of the forum for it.

[KodeToad]

So, I made 3 transactions all resulting in the same outcome. I didn't realise at the time that placing an offer would result in a fee even if the placement wasn't successful. I'd consider this a bug since it shouldn't be reading that AccountAgeWitnessStore data after the transaction is placed. Now, I'd like a way to test it without incurring anymore fees if that's possible. I've recompiled it and restarted it but I'm reluctant to do any more tests at this point. I checked the age of the account and it looks fine, but it did at first as well. What do you mean " ping me on slack of the forum"?

[ghost]

@KodeToad , Bisq has also a slack chat. The link for an invite is : https://bisq.network/slack-invite

[ManfredKarrer]

@KodeToad You can run Bisq in developer mode (regtest, localhost). See: https://github.com/bisq-network/bisq-desktop/wiki/4.1.-How-to-prepare-your-Bisq-source-code-for-regtest-mode

I am sorry for the lost fees but I never saw that bug before. Maybe some local data on your side is corrupted. You can also start Bisq with a new fresh data directory when passing --appName=Bisq2 (or whatever). Have you tried as well to delete the AccountAgeWitnessStore file? u can open the data directory at account/backup.

[KodeToad]

My bad. That was the old error. What does this mean?

Aug-10 22:51:21.742 [JavaFX Application Thread] INFO  b.d.app.BisqApp: System load: Memory (MB)): 336 / No. of threads: 58 
Aug-10 22:51:27.245 [JavaFX Application Thread] WARN  b.c.b.w.TxBroadcaster: Broadcast of tx 452efd47702ea4c011d32bc713069d0c41bd514003c40031f8fa16d271a063f9 not completed after 8 sec. We optimistically assume that the tx broadcast succeeded and call onSuccess on the callback handler. 
Aug-10 22:51:27.248 [JavaFX Application Thread] ERROR b.c.b.w.TxBroadcaster: TxBroadcaster.onTimeout TxBroadcastTimeoutException{
     localTx=  452efd47702ea4c011d32bc713069d0c41bd514003c40031f8fa16d271a063f9
     in   PUSHDATA(72)[3045022100dc5b302564ca540a0c2dab3c987206b2bb23d3ad0f16fa7c71bd676073d5332902201a25fb1c5d992c8077e6c478f49a6f7275fe8cf3d783e741e432e826497152c501] PUSHDATA(33)[031155884af64934b6d8b6abd0e786dfde505c1e2ea2b4fb34b61d06ccac0541ee] 0.0655 BTC (6550000)
          outpoint:40bcb2d5b42bb6fe6f676117fde8e594f1417e22b4ec7510af0152e6f0a7635a:1 hash160:69bd0300f31e260d611ff6e468b2d6dea6e283c7
     in   PUSHDATA(71)[30440220570d5f6dec778dafbadeae7a183f567a853f18bfe5584396ad80bdc8375ebb3402203c199b4bb216eaa34c161b0e73269309bb31d58acff7dc450de9affe0beca40901] PUSHDATA(33)[036f5a5553c9e9c387762cf124cc2bf92fb1eb9a0eb3747c0d5586e82f6e68debb] 0.0655 BTC (6550000)
          outpoint:d76a20b167325458e93231048b19c7a7b0a4edcd1d6f2b1b80ab7a9dd039a04b:1 hash160:e4cdf458bf24b15ad56ffbe8ea7315d7ae224821
     out  DUP HASH160 PUSHDATA(20)[4fceee700a31f782ba4f9ebd2b127cd400041bb1] EQUALVERIFY CHECKSIG 0.000125 BTC (12500) ScriptPubKey: 76a9144fceee700a31f782ba4f9ebd2b127cd400041bb188ac Address:18GzH11T5h2fpvUoBJDub7MgNJVw3FfqQ8 
     out  DUP HASH160 PUSHDATA(20)[3c62f452e0e45c3a6518169bae654146045bbd9c] EQUALVERIFY CHECKSIG 0.0655 BTC (6550000) ScriptPubKey: 76a9143c62f452e0e45c3a6518169bae654146045bbd9c88ac Address:16WJ5yvGSqwjG54EksTTvoeUjsgY8fxiGh 
     out  DUP HASH160 PUSHDATA(20)[8e1a14ea04f8742c56617c3f253471e2f61b4c86] EQUALVERIFY CHECKSIG 0.0653344 BTC (6533440) ScriptPubKey: 76a9148e1a14ea04f8742c56617c3f253471e2f61b4c8688ac Address:1DxNCRpWniGNYGLh313bbSMneYcHD2V176 
     fee  0.0000406 BTC for 407 bytes (9 Satoshi/Byte)
     prps USER_PAYMENT
,
     delay=8
} TxBroadcastException{
     txId='null'
} bisq.core.btc.wallet.TxBroadcastTimeoutException: The transaction was not broadcasted in 8seconds. txId=452efd47702ea4c011d32bc713069d0c41bd514003c40031f8fa16d271a063f9 
Aug-10 22:51:27.249 [JavaFX Application Thread] ERROR b.c.t.Task: An error occurred at task: CreateMakerFeeTx
Exception message: The transaction was not broadcasted in 8seconds. txId=452efd47702ea4c011d32bc713069d0c41bd514003c40031f8fa16d271a063f9 
Aug-10 22:51:27.250 [JavaFX Application Thread] ERROR b.c.t.TaskRunner: Task failed: CreateMakerFeeTx / errorMessage: An error occurred at task: CreateMakerFeeTx
Exception message: The transaction was not broadcasted in 8seconds. txId=452efd47702ea4c011d32bc713069d0c41bd514003c40031f8fa16d271a063f9 
Aug-10 22:51:27.250 [JavaFX Application Thread] ERROR b.c.o.p.PlaceOfferProtocol: An error occurred at task: CreateMakerFeeTx
Exception message: The transaction was not broadcasted in 8seconds. txId=452efd47702ea4c011d32bc713069d0c41bd514003c40031f8fa16d271a063f9 
Aug-10 22:51:27.250 [JavaFX Application Thread] ERROR b.d.m.o.c.CreateOfferDataModel: An error occurred at task: CreateMakerFeeTx
Exception message: The transaction was not broadcasted in 8seconds. txId=452efd47702ea4c011d32bc713069d0c41bd514003c40031f8fa16d271a063f9 
Aug-10 22:51:42.247 [JavaFX Application Thread] INFO  b.c.p.p.PriceFeedService: request from provider http://44mgyoe2b6oqiytt.onion/ 61.01 sec. after last request 

[ManfredKarrer]

If the tx was not broadcasted successfully it reports that timeout error. That can happen if network or Tor is unstable (in December when Tor had DDoS attacks we had more of those problems, but since that is over it happens rarely. Usually BitcoinJ republishes the tx at next startup, but that could be too late if another use is taking the offer. It also can be that the timeout get triggered too early and the tx gets broadcasted but needed more time. All in all its an open issue and if any developer who ideally is knowledgeable with BitcoinJ could work on that would be great! As those bugs are overall rare it is not on my own high prio list (need to get the DAO finished). Btw. If you want to try again with mainnet you can make a test offer with very low amount (0.0001 BTC) and low spread (0% from market price), then the fee is super low (about a few cents).

[ManfredKarrer]

Do you have a stable internet connection? Are the nr. of BTC and P2P network nodes > 8 in the left and right bottom?

[KodeToad]

It has happens every time. That's times 4 now. Yes, the internet connection is stable. Bisq is incredibly unstable at startup. If I'm slow, entering the password can take several minutes. This time after startup, BTC clients 9, P2P clients 13. Are there any practical things I can to to reduce the risk of this happening?

[ManfredKarrer]

@KodeToad Do you have a very slow machine or very low RAM? Entering pw takes usually less then a second to derive the key. No idea what causes the issues but easiest would be if you start over with a new data directory. See https://bisq.community/t/switching-to-a-new-data-directory/1697 and https://bisq.community/t/carry-over-account-age-witness-to-new-data-directory/5605 (if u have an older account)

[KodeToad]

Wallet Password to sign in and unlock the console

[KodeToad]

The backup directory is a bit slow, but no to those other things. I'll look into it and get back to you.

[ghost]

You should give us the exact characteristics of the machine. This may help. And perhaps help others. How much RAM does this machine have ? And also, what is your connection type ? cable/cable, wifi/wifi, etc. Bisq is rather demanding concerning the internet connection.

[KodeToad]

12G Ram 2 processors Manjaro on VBox ADSL2 with 8 to 12 MBps. Several other apps are running, but they don't have responsiveness issues.

[ghost]

This should really be sufficient. Maybe you could have a look at the system monitor to get more informations. In normal working, Bisq consumes less then 5% CPU and less than 1GB RAM see eg : https://www.reddit.com/r/bisq/comments/96wnpc/bisq_cpu_ram_consumption_answer_to_bisq_in_a_vm/

[ManfredKarrer]

RAM depends on whats available. java is greedy so if u have much ram it takes much but it still works with little ram. i think about 300 MB is min. but on my machine its up to 2 GB as i have lot of ram...

[ghost]

On a 16GB PC, I have a Bisq which consumes 1000 MB. On a 8GB PC, another Bisq consumes 750 MB. Both under Debian 64 bits. Running pure vanilla Bisq. No arguments etc. ... maybe there is something missing in my config ?

[ManfredKarrer]

That sounds ok. Over time it might increase RAM, but as said it takes what it available if there is not much ram all is ok as well, might be just a bit slower when switching screens or so.

[ghost]

Now it's 500MB RAM on the 16GB PC. It even bottomed at 300 MB. And Bisq is the only app running on this PC.

[rudygodoy]

I had similar exception with existing profiles after syncing with the latest master. The exception is gone after wiping out existing profiles, which is not desired. In my case the AccountAgeWitnessStore file was not present.

[KodeToad]

@ManfredKarrer, when importing the FiatPaymentAccounts account data, should the Account Age be reset to 0 days?

[ManfredKarrer]

@KodeToad You need to copy over also the signature key. See here: https://bisq.community/t/carry-over-account-age-witness-to-new-data-directory/5605

[KodeToad]

Nah. Even with the new account, same as before. The software just doesn't work here. I have 12 p2p peers and 9 btc peers. Why is there an 8 second timeout anyway? Couldn't waiting a bit longer alleviate the problem? What can I try next? Btw, a smaller amount didn't help at all.

Aug-20 22:57:30.499 [JavaFX Application Thread] INFO  b.c.p.p.PriceFeedService: request from provider http://44mgyoe2b6oqiytt.onion/ 64.013 sec. after last request 
Aug-20 22:57:32.217 [JavaFX Application Thread] INFO  b.c.p.p.PriceFeedService: Received new MarketPrice(currencyCode=USD, price=6450.62, timestampSec=1534769797550, isExternallyProvidedPrice=true) from provider http://xc3nh4juf2hshy7e.onion/ after 1.716 sec. 
Aug-20 22:57:36.136 [JavaFX Application Thread] WARN  b.c.b.w.TxBroadcaster: Broadcast of tx 557a1c5760472c15726c22549b7a3ddf3826b7c8f9a960c3ecb11439f9e8bac3 not completed after 8 sec. We optimistically assume that the tx broadcast succeeded and call onSuccess on the callback handler. 
Aug-20 22:57:36.140 [JavaFX Application Thread] ERROR b.c.b.w.TxBroadcaster: TxBroadcaster.onTimeout TxBroadcastTimeoutException{
     localTx=  557a1c5760472c15726c22549b7a3ddf3826b7c8f9a960c3ecb11439f9e8bac3
     in   PUSHDATA(71)[304402204befbc647d0bc043b4a718391535e04160783b643c24298a38164e2d2e27b80a022032c49a9fd8d51c99dead63960023a5b64c8876d351f3dd738d5edf0d78b5217d01] PUSHDATA(33)[0233d93dacae3e9b62a7203c46ac2a4ee94732faf42145f0a511688e86050d2cc4] 1.00429807 BTC (100429807)
          outpoint:3e3ac6a428013df944d7a3aa9d0ab988f8a52407ece886a53ae1d99b2bac60f2:0 hash160:f7e1862ec4116456f75666f4a74f06dbfa922674
     out  DUP HASH160 PUSHDATA(20)[4fceee700a31f782ba4f9ebd2b127cd400041bb1] EQUALVERIFY CHECKSIG 0.00005 BTC (5000) ScriptPubKey: 76a9144fceee700a31f782ba4f9ebd2b127cd400041bb188ac Address:18GzH11T5h2fpvUoBJDub7MgNJVw3FfqQ8 
     out  DUP HASH160 PUSHDATA(20)[b986ba163cc92e9d168f921333d939e1bf116030] EQUALVERIFY CHECKSIG 0.0031 BTC (310000) ScriptPubKey: 76a914b986ba163cc92e9d168f921333d939e1bf11603088ac Address:1HuyQUia9c4yZj31UQvNBKRQbCFuEdFv9G 
     out  DUP HASH160 PUSHDATA(20)[62f75a757ecfd0e318d3df4f42bc002a97a4ded3] EQUALVERIFY CHECKSIG 1.00112207 BTC (100112207) ScriptPubKey: 76a91462f75a757ecfd0e318d3df4f42bc002a97a4ded388ac Address:1A2HYDHXHAf6EB3XRAdztzp89jRHa7PaaV 
     fee  0.000026 BTC for 259 bytes (10 Satoshi/Byte)
     prps USER_PAYMENT
,
     delay=8
} TxBroadcastException{
     txId='null'
} bisq.core.btc.wallet.TxBroadcastTimeoutException: The transaction was not broadcasted in 8seconds. txId=557a1c5760472c15726c22549b7a3ddf3826b7c8f9a960c3ecb11439f9e8bac3 
Aug-20 22:57:36.141 [JavaFX Application Thread] ERROR b.c.t.Task: An error occurred at task: CreateMakerFeeTx
Exception message: The transaction was not broadcasted in 8seconds. txId=557a1c5760472c15726c22549b7a3ddf3826b7c8f9a960c3ecb11439f9e8bac3 
Aug-20 22:57:36.142 [JavaFX Application Thread] ERROR b.c.t.TaskRunner: Task failed: CreateMakerFeeTx / errorMessage: An error occurred at task: CreateMakerFeeTx
Exception message: The transaction was not broadcasted in 8seconds. txId=557a1c5760472c15726c22549b7a3ddf3826b7c8f9a960c3ecb11439f9e8bac3 
Aug-20 22:57:36.143 [JavaFX Application Thread] ERROR b.c.o.p.PlaceOfferProtocol: An error occurred at task: CreateMakerFeeTx
Exception message: The transaction was not broadcasted in 8seconds. txId=557a1c5760472c15726c22549b7a3ddf3826b7c8f9a960c3ecb11439f9e8bac3 
Aug-20 22:57:36.143 [JavaFX Application Thread] ERROR b.d.m.o.c.CreateOfferDataModel: An error occurred at task: CreateMakerFeeTx
Exception message: The transaction was not broadcasted in 8seconds. txId=557a1c5760472c15726c22549b7a3ddf3826b7c8f9a960c3ecb11439f9e8bac3 
Aug-20 22:58:32.522 [JavaFX Application Thread] INFO  b.c.p.p.PriceFeedService: request from provider http://44mgyoe2b6oqiytt.onion/ 62.02 sec. after last request 
Aug-20 22:58:34.347 [JavaFX Application Thread] INFO  b.c.p.p.PriceFeedService: Received new MarketPrice(currencyCode=USD, price=6454.35, timestampSec=1534769887510, isExternallyProvidedPrice=true) from provider http://xc3nh4juf2hshy7e.onion/ after 1.824 sec. 

[ManfredKarrer]

@KodeToad If Bisq is so slow at startup and unstable it seems your environment is somehow too restricted. On a normal system it runs without such issues. The reported bug with the failed tx is probably a result of that constrained environment. Do you have an alternative where you can try it out. There are > 10000 downloads every version and for those it works fine, so it seems to be caused by the environment you are using (will be still a bug which gets triggered by that though... but it will be very hard to reproduce)

[KodeToad]

What is this supposed to mean? "... not completed after 8 sec. We optimistically assume that the tx broadcast succeeded and call onSuccess on the callback handler." But the callback handler throws an error even though the transaction is complete?

[KodeToad]

It starts up ok. It's just that I can't add an offer because of this. 5 attempt, 5 failures

[ManfredKarrer]

@KodeToad If we don't get the tx broadcasted after 8 sec. it returns with a success. Often it gets successfully broadcasted but a bit delayed. In cases when it does not get broadcasted at all (as it seems in your case) then it will end up in a failed offer. You posted earlier that entering the pw at startup takes a long time. That is not normal and I assume that your environment is too restricted (too low RAM or CPU). Do u run it in a VM? If u had a chance to run it on another machine I would recommend to try that out.

[ghost]

@KodeToad could you have a look at the system monitor to get more informations. In normal working, Bisq consumes less then 5% CPU and less than 1GB RAM see eg : https://www.reddit.com/r/bisq/comments/96wnpc/bisq_cpu_ram_consumption_answer_to_bisq_in_a_vm/

[KodeToad]

This is the first time I've used Bisq so I'm not familiar and I hope I'm not missing anything. This is a recommended distribution. bisq-git 0.7.1.r16.g70e086d41-1, built and installed 8/8/18. I spoke to the Manjaro maintainers, and they said it was an issue to take up with the developers.

I completely reinstalled according to your recommended method 9 days ago. I carried over the age witness as you recommended. Everything worked fine. I now have 2 instances running. The new instance did complain of old tor peer data and I allowed it to renew that. Timed startup at 1 minute. 8 seconds to render the gui and a further 51 to connect tor. I do use a vm, but it has plenty of rss and you have said this should be sufficient.

I'd like to try it on another machine but it might take a while. It depends on the Inno Windows 8.1 compiler. Can I install everything as an unprivileged user?

[ghost]

You mean you have 2 instances running simultaneously on the same computer ? If this is the case and you didn't do it properly, there will be mandatory conflicts. Because both instances use the same directory.

Even if you do it properly, Bisq uses internet rather heavily (internet+P2P+Tor). When I run 2 Bisq instances, I see my internet bandwidth strongly used.

[KodeToad]

I did it properly, but I ran the transactions with only one instance running.

[ghost]

If you have 2 Bisq instances, even non running at same time, you should also have 2 applications separate directories. The default path is ~/.local/share/Bisq. So you should have eg ~/.local/share/Bisq1 and ~/.local/share/Bisq2 If this is not the case, there may be conflicts and bad mixing. If you begin with Bisq, this is really not the most recommended practice.

[KodeToad]

Of course, that's not the problem. This problem has occurred since a fresh install. I was hoping you could answer the question about the 3rd party software requirement Inno. Is it possible to install this as a non privileged user?

[ManfredKarrer]

@KodeToad I found the issue for both the InvalidProtocolBufferException and the tx broadcast failures. And they are fixed in the upcoming release. Hope we can release tomorrow. The fixes are partly merged to master but still soem PR are open. So better to wait one day and then u can use latest master or the new release. Please feel free to ping me on Slack or Forum with a PM so I can reimburse you for the lost trade fees.

[KodeToad]

If it works, I'll be happy to contribute to fees. I'll let you know how it goes.

[KodeToad]

:'(

Aug-23 15:10:30.807 [JavaFX Application Thread] INFO  o.b.w.Wallet: Completing send tx with 2 outputs totalling 0.00805 BTC and a fee of 0.00 BTC/kB 
Aug-23 15:10:30.811 [JavaFX Application Thread] INFO  o.b.w.Wallet:   with 0.99304607 BTC change 
Aug-23 15:10:30.840 [JavaFX Application Thread] INFO  o.b.w.Wallet:   with a fee of 0.0001 BTC/kB, 0.000026 BTC for 260 bytes 
Aug-23 15:10:30.841 [JavaFX Application Thread] INFO  o.b.w.Wallet:   completed:   89a87fbea9f69851de62d18612efa7b0a052c8be27889b1f77f69d83ecb6163f
     in   PUSHDATA(72)[304502210088a544de5ec6b9fb369eca20ade24275dde6e454abfd6483dd28c773c3176a180220128bf789baeefb47e6767d0f8094d58052a9bf6f42d3ea895a1e5081266a0acd01] PUSHDATA(33)[03d258622abf9fd580743f8fd51c72285fc582130349151c53ed5156fa73ee1984] 1.00112207 BTC (100112207)
          outpoint:557a1c5760472c15726c22549b7a3ddf3826b7c8f9a960c3ecb11439f9e8bac3:2 hash160:62f75a757ecfd0e318d3df4f42bc002a97a4ded3
     out  DUP HASH160 PUSHDATA(20)[830017d0dfc9f6602ca60988afc0b651fccc65f2] EQUALVERIFY CHECKSIG 0.00005 BTC (5000) ScriptPubKey: 76a914830017d0dfc9f6602ca60988afc0b651fccc65f288ac Address:1CwfdbSALpQykvb5KLQJm5p8GFCPQefSAf 
     out  DUP HASH160 PUSHDATA(20)[c5f1f09e48efa336b39a2d301b15e62e81745989] EQUALVERIFY CHECKSIG 0.008 BTC (800000) ScriptPubKey: 76a914c5f1f09e48efa336b39a2d301b15e62e8174598988ac Address:1K3dx56XKtyCvFUsvPmPaHnJz2cBMwNDPy 
     out  DUP HASH160 PUSHDATA(20)[de0f85f6296b090307f4df9822cfa99862c3e1bd] EQUALVERIFY CHECKSIG 0.99304607 BTC (99304607) ScriptPubKey: 76a914de0f85f6296b090307f4df9822cfa99862c3e1bd88ac Address:1MF9cAUEm99m4aJDdP3HgWBmHEQrNgt6jg 
     fee  0.000026 BTC for 260 bytes (10 Satoshi/Byte)
     prps USER_PAYMENT

Aug-23 15:10:30.847 [JavaFX Application Thread] INFO  b.d.m.o.c.CreateOfferDataModel: feeTxSize 260 bytes 
Aug-23 15:10:30.847 [JavaFX Application Thread] INFO  b.d.m.o.c.CreateOfferDataModel: txFee based on estimated size: 0.000026 BTC, recommended txFee is 10 sat/byte 
Aug-23 15:10:42.301 [JavaFX Application Thread] INFO  b.c.p.p.PriceFeedService: request from provider http://5bmpx76qllutpcyp.onion/ 62.013 sec. after last request 
Aug-23 15:10:43.710 [JavaFX Application Thread] INFO  b.c.p.p.PriceFeedService: Received new MarketPrice(currencyCode=USD, price=6398.62, timestampSec=1535001070522, isExternallyProvidedPrice=true) from provider http://44mgyoe2b6oqiytt.onion/ after 1.393 sec. 
Aug-23 15:11:34.973 [JavaFX Application Thread] INFO  b.c.p.f.FeeService: BTC tx fee: txFeePerByte=10 
Aug-23 15:11:45.351 [JavaFX Application Thread] INFO  b.c.p.p.PriceFeedService: request from provider http://5bmpx76qllutpcyp.onion/ 63.034 sec. after last request 
Aug-23 15:11:46.943 [JavaFX Application Thread] INFO  b.c.p.p.PriceFeedService: Received new MarketPrice(currencyCode=USD, price=6398.62, timestampSec=1535001070522, isExternallyProvidedPrice=true) from provider http://44mgyoe2b6oqiytt.onion/ after 1.591 sec. 
Aug-23 15:12:07.262 [JavaFX Application Thread] INFO  b.c.t.TaskRunner: Run task: ValidateOffer 
Aug-23 15:12:07.271 [JavaFX Application Thread] INFO  b.c.t.TaskRunner: Run task: CreateMakerFeeTx 
Aug-23 15:12:07.291 [JavaFX Application Thread] INFO  b.c.b.w.TradeWalletService: reservedFundsForOffer 0.008 
Aug-23 15:12:07.292 [JavaFX Application Thread] INFO  b.c.b.w.TradeWalletService: tradingFee 0.00005 
Aug-23 15:12:07.293 [JavaFX Application Thread] INFO  b.c.b.w.TradeWalletService: txFee 0.000026 
Aug-23 15:12:07.294 [JavaFX Application Thread] INFO  o.b.w.Wallet: Completing send tx with 2 outputs totalling 0.00805 BTC and a fee of 0.00 BTC/kB 
Aug-23 15:12:07.296 [JavaFX Application Thread] INFO  o.b.w.Wallet:   with 0.99304607 BTC change 
Aug-23 15:12:07.306 [JavaFX Application Thread] INFO  o.b.w.Wallet:   with a fee of 0.0001 BTC/kB, 0.000026 BTC for 260 bytes 
Aug-23 15:12:07.306 [JavaFX Application Thread] INFO  o.b.w.Wallet:   completed:   b6ca0bc04d279f8813eaa5f4ee91b42cf33fc589405cfcbd60f07798722827aa
     in   PUSHDATA(72)[3045022100a78006c5534a5f6d13b4acc71a142295a60086c94cb315efe60f0d4e0ea57f7502203f14bd086d9b9a3e0c3ca1ea87dbd638550e5c1ab2b7cfabbe6a086ea1fe769201] PUSHDATA(33)[03d258622abf9fd580743f8fd51c72285fc582130349151c53ed5156fa73ee1984] 1.00112207 BTC (100112207)
          outpoint:557a1c5760472c15726c22549b7a3ddf3826b7c8f9a960c3ecb11439f9e8bac3:2 hash160:62f75a757ecfd0e318d3df4f42bc002a97a4ded3
     out  DUP HASH160 PUSHDATA(20)[4fceee700a31f782ba4f9ebd2b127cd400041bb1] EQUALVERIFY CHECKSIG 0.00005 BTC (5000) ScriptPubKey: 76a9144fceee700a31f782ba4f9ebd2b127cd400041bb188ac Address:18GzH11T5h2fpvUoBJDub7MgNJVw3FfqQ8 
     out  DUP HASH160 PUSHDATA(20)[c5f1f09e48efa336b39a2d301b15e62e81745989] EQUALVERIFY CHECKSIG 0.008 BTC (800000) ScriptPubKey: 76a914c5f1f09e48efa336b39a2d301b15e62e8174598988ac Address:1K3dx56XKtyCvFUsvPmPaHnJz2cBMwNDPy 
     out  DUP HASH160 PUSHDATA(20)[de0f85f6296b090307f4df9822cfa99862c3e1bd] EQUALVERIFY CHECKSIG 0.99304607 BTC (99304607) ScriptPubKey: 76a914de0f85f6296b090307f4df9822cfa99862c3e1bd88ac Address:1MF9cAUEm99m4aJDdP3HgWBmHEQrNgt6jg 
     fee  0.000026 BTC for 260 bytes (10 Satoshi/Byte)
     prps USER_PAYMENT

Aug-23 15:12:07.311 [JavaFX Application Thread] INFO  b.c.b.w.WalletService: 
tradingFeeTx:
  b6ca0bc04d279f8813eaa5f4ee91b42cf33fc589405cfcbd60f07798722827aa
     in   PUSHDATA(72)[3045022100a78006c5534a5f6d13b4acc71a142295a60086c94cb315efe60f0d4e0ea57f7502203f14bd086d9b9a3e0c3ca1ea87dbd638550e5c1ab2b7cfabbe6a086ea1fe769201] PUSHDATA(33)[03d258622abf9fd580743f8fd51c72285fc582130349151c53ed5156fa73ee1984] 1.00112207 BTC (100112207)
          outpoint:557a1c5760472c15726c22549b7a3ddf3826b7c8f9a960c3ecb11439f9e8bac3:2 hash160:62f75a757ecfd0e318d3df4f42bc002a97a4ded3
     out  DUP HASH160 PUSHDATA(20)[4fceee700a31f782ba4f9ebd2b127cd400041bb1] EQUALVERIFY CHECKSIG 0.00005 BTC (5000) ScriptPubKey: 76a9144fceee700a31f782ba4f9ebd2b127cd400041bb188ac Address:18GzH11T5h2fpvUoBJDub7MgNJVw3FfqQ8 
     out  DUP HASH160 PUSHDATA(20)[c5f1f09e48efa336b39a2d301b15e62e81745989] EQUALVERIFY CHECKSIG 0.008 BTC (800000) ScriptPubKey: 76a914c5f1f09e48efa336b39a2d301b15e62e8174598988ac Address:1K3dx56XKtyCvFUsvPmPaHnJz2cBMwNDPy 
     out  DUP HASH160 PUSHDATA(20)[de0f85f6296b090307f4df9822cfa99862c3e1bd] EQUALVERIFY CHECKSIG 0.99304607 BTC (99304607) ScriptPubKey: 76a914de0f85f6296b090307f4df9822cfa99862c3e1bd88ac Address:1MF9cAUEm99m4aJDdP3HgWBmHEQrNgt6jg 
     fee  0.000026 BTC for 260 bytes (10 Satoshi/Byte)
     prps USER_PAYMENT

Aug-23 15:12:07.334 [JavaFX Application Thread] INFO  o.b.c.TransactionBroadcast: Waiting for 4 peers required for broadcast, we have 9 ... 
Aug-23 15:12:07.338 [JavaFX Application Thread] INFO  o.b.c.TransactionBroadcast: broadcastTransaction: We have 9 peers, adding b6ca0bc04d279f8813eaa5f4ee91b42cf33fc589405cfcbd60f07798722827aa to the memory pool 
Aug-23 15:12:07.338 [JavaFX Application Thread] INFO  o.b.c.TransactionBroadcast: Sending to 5 peers, will wait for 2, sending to: [fz6nsij6jiyuwlsc.onion]:8333,[3xucqntxp5ddoaz5.onion]:8333,[mxdtrjhe2yfsx3pg.onion]:8333,[4jyh6llqj264oggs.onion]:8333,[z33nukt7ngik3cpe.onion]:8333 
Aug-23 15:12:11.144 [JavaFX Application Thread] INFO  o.b.c.TransactionBroadcast: broadcastTransaction: SEEN_PEERS:  TX b6ca0bc04d279f8813eaa5f4ee91b42cf33fc589405cfcbd60f07798722827aa seen by 1 peers 
Aug-23 15:12:11.236 [JavaFX Application Thread] INFO  o.b.c.TransactionBroadcast: broadcastTransaction: SEEN_PEERS:  TX b6ca0bc04d279f8813eaa5f4ee91b42cf33fc589405cfcbd60f07798722827aa seen by 2 peers 
Aug-23 15:12:11.236 [JavaFX Application Thread] INFO  o.b.c.TransactionBroadcast: broadcastTransaction: b6ca0bc04d279f8813eaa5f4ee91b42cf33fc589405cfcbd60f07798722827aa complete 
Aug-23 15:12:11.241 [JavaFX Application Thread] INFO  o.b.w.Wallet: Received a pending transaction b6ca0bc04d279f8813eaa5f4ee91b42cf33fc589405cfcbd60f07798722827aa that spends 1.00112207 BTC from our own wallet, and sends us 1.00104607 BTC 
Aug-23 15:12:11.241 [JavaFX Application Thread] INFO  o.b.w.Wallet: commitTx of b6ca0bc04d279f8813eaa5f4ee91b42cf33fc589405cfcbd60f07798722827aa 
Aug-23 15:12:11.243 [JavaFX Application Thread] INFO  o.b.w.Wallet:   marked 557a1c5760472c15726c22549b7a3ddf3826b7c8f9a960c3ecb11439f9e8bac3:2 as spent by b6ca0bc04d279f8813eaa5f4ee91b42cf33fc589405cfcbd60f07798722827aa 
Aug-23 15:12:11.243 [JavaFX Application Thread] INFO  o.b.w.Wallet: ->pending: b6ca0bc04d279f8813eaa5f4ee91b42cf33fc589405cfcbd60f07798722827aa 
Aug-23 15:12:11.243 [JavaFX Application Thread] INFO  o.b.w.Wallet: Estimated balance is now: 1.00414607 BTC 
Aug-23 15:12:11.248 [JavaFX Application Thread] INFO  o.b.w.WalletFiles: Saving wallet; last seen block is height 538053, date 2018-08-23T04:36:43Z, hash 0000000000000000000bd7c4ee96cf6cc4c910835f81caac8a6077606028bc20 
Aug-23 15:12:11.285 [JavaFX Application Thread] INFO  o.b.w.WalletFiles: Save completed in 36.44 ms 
Aug-23 15:12:11.298 [JavaFX Application Thread] INFO  b.c.b.w.BtcWalletService: swap addressEntry with address 17eHnvbquGtmcPwZETcp5uVb8PpxxafmJk and offerId lebzfgs-d264e492-c73e-4f32-8645-a583cc84ec44-080 from context OFFER_FUNDING to available 
Aug-23 15:12:11.299 [JavaFX Application Thread] INFO  b.c.t.TaskRunner: Run task: AddToOfferBook 
Aug-23 15:12:11.315 [JavaFX Application Thread] ERROR b.c.t.Task: An error occurred at task: AddToOfferBook
Exception message: Element at index 0 is null. 
Aug-23 15:12:11.315 [JavaFX Application Thread] ERROR b.c.t.TaskRunner: Task failed: AddToOfferBook / errorMessage: An error occurred at task: AddToOfferBook
Exception message: Element at index 0 is null. 
Aug-23 15:12:11.315 [JavaFX Application Thread] ERROR b.c.o.p.PlaceOfferProtocol: An error occurred at task: AddToOfferBook
Exception message: Element at index 0 is null. 
Aug-23 15:12:11.315 [JavaFX Application Thread] ERROR b.d.m.o.c.CreateOfferDataModel: An error occurred at task: AddToOfferBook
Exception message: Element at index 0 is null. 

[ManfredKarrer]

That is another issue now. It might be related to the failed trades. Could you try with a fresh installation?
See: https://bisq.community/t/switching-to-a-new-data-directory/1697 https://bisq.community/t/carry-over-account-age-witness-to-new-data-directory/5605

[KodeToad]

Can I try to restore the seed from the old wallet, or is that wallet what's causing the problem?

[ManfredKarrer]

@KodeToad Restore is only for emergency. It will not recreate the internal wallet so please dont do that as that might likely lead to problems. Just make a new fresh install and send over the btc. miner fees are low atm luckily...

[KodeToad]

It looks like I can place an offer before confirmations are complete. Also, the interface to place an offer won't let me put amounts larger than 0.25btc. Why? If I enter 0.25btc the I get another message about my trade limit. Seems pointless.

[KodeToad]

It's working this time :)

[ghost]

@KodeToad wrote:

Also, the interface to place an offer won't let me put amounts larger than 0.25btc. Why? If I enter 0.25btc the I get another message about my trade limit. Seems pointless.

See the FAQ : What are the trade limits -> https://bisq.network/faq/#3

[KodeToad]

That's fair I suppose considering the dispute process. I wonder why it doesn't give me the actual trade limit the first time.

[ManfredKarrer]

@KodeToad u see your trade limit if u select the payment account at accounts/... if its not as expected then u have not taken over the signature key.

[KodeToad]

When I put over 0.25btc it says that is the limit. I then change it to less than 0.25btc and more than the trade limit, I get a new message telling me the trade limit. Why not just show the trade limit or the lowest number to begin with? The way it is misleads you the first time into thinking you can use 0.25btc even if you have a trade limit lower than that.

[ManfredKarrer]

Thats a bug in the validation code...

[KodeToad]

Thanks

[ghost]

@KodeToad , Since you are using Bisq on Manjaro, would it be possible for you to describe (precisely) the exact procedure you used to install Bisq ? Did you just follow the arch linux downloading procedure, or there are some special issues specific to Manjaro ? This would be kind and could help other people with Manjaro to also try Bisq. Thanks