-
alcapaca
Hello, I am trying to make a Monero Flutter plugin so that monero wallets can more easily be made in flutter projects.
-
alcapaca
I am able to make wallets, restore them, and send transactions so far, but I have run into a pretty serious native crash.
-
alcapaca
When I restore a wallet sometimes it will crash with the following error.
-
alcapaca
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
-
alcapaca
Build fingerprint: 'google/taimen/taimen:11/RP1A.201005.004.A1/6934943:user/release-keys'
-
alcapaca
Revision: 'rev_10'
-
alcapaca
ABI: 'arm64'
-
alcapaca
Timestamp: 2022-05-05 13:29:07+0800
-
alcapaca
pid: 4323, tid: 4415, name: DartWorker >>> com.example.flutter_libmonero_example <<<
-
alcapaca
uid: 10435
-
alcapaca
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
-
alcapaca
Cause: null pointer dereference
-
alcapaca
x0 00000077dc66e27c x1 0000000000000000 x2 0000000000000020 x3 00000077dc90dfc0
-
alcapaca
x4 0000000000000020 x5 00000077dc66e29c x6 6ba45c57ecedc839 x7 7b693b97342475af
-
alcapaca
x8 000000000029fdc3 x9 000000000000001f x10 0000000000001b08 x11 00000077dc30e040
-
alcapaca
x12 f23b9fa7f5b2b920 x13 5ab56bcd7a095991 x14 0018b6584180a81a x15 000000000a516280
-
alcapaca
x16 00000077f1367f90 x17 0000007b077e8000 x18 00000000000bb9d5 x19 0000000000000020
-
alcapaca
x20 0000000000000000 x21 0000000000000000 x22 00000077f1c6fc28 x23 0000000000000020
-
alcapaca
x24 00000077f1c71000 x25 00000077f12e9578 x26 00000077f12e9328 x27 00000077f12e94c8
-
alcapaca
x28 00000077f1c6fc10 x29 00000077f1c6fab0
-
alcapaca
lr 00000077f0844d00 sp 00000077f1c6fa80 pc 0000007b077e7eb0 pst 0000000080000000
-
hyc
use a pastebin
-
alcapaca
-
alcapaca
I can trace the error back to the wallet2::get_cache_file_data function, and I think it is occuring at
github.com/monero-project/monero/bl…master/src/wallet/wallet2.cpp#L5802
-
alcapaca
it seems that in memcpy it tries to derefrence a null pointer, when the wallet is being serialized which causes the crash, however I dont really have an idea why this would happen.
-
moneromooo
alcapaca: Try building with -O0 -g and getting a stack trace.
-
ErCiccione
-
moneromooo
If you can't get a stack trace, printf all over the place repeatedly is what I do.
-
xxfedexx[m]
I have got a question about the upcoming Monero view tags
-
xxfedexx[m]
If you have the wallet A, and you want to transfer money to wallet B, the view tag included in the tx is A's or B's or both?
-
xxfedexx[m]
And wouldn't it decrease privacy?
-
sethforprivacy
> <@xxfedexx:matrix.org> I have got a question about the upcoming Monero view tags
-
sethforprivacy
> If you have the wallet A, and you want to transfer money to wallet B, the view tag included in the tx is A's or B's or both?
-
sethforprivacy
> And wouldn't it decrease privacy?
-
sethforprivacy
Not a topic for this channel, but hopefully this answers your Qs:
localmonero.co/knowledge/view-tags-reduce-monero-sync-time
-
xxfedexx[m]
Thanks, but it says:
-
xxfedexx[m]
> add a 1-byte “tag” to each transaction using a shared secret known only to the sender and receiver of that transaction.
-
xxfedexx[m]
That secret gets regenerated on each transaction with the wallet keys?
-
xxfedexx[m]
* Thanks, but it says:
-
xxfedexx[m]
> add a 1-byte “tag” to each transaction using a shared secret known only to the sender and receiver of that transaction.
-
xxfedexx[m]
That secret gets regenerated on each transaction with the wallet keys?
-
xxfedexx[m]
How can the receiver know it too?
-
xxfedexx[m]
* Thanks, but it says:
-
xxfedexx[m]
> add a 1-byte “tag” to each transaction using a shared secret known only to the sender and receiver of that transaction.
-
xxfedexx[m]
That secret gets regenerated on each transaction with the wallet keys?
-
xxfedexx[m]
nevermind, the localmonero post is not clear but the github issue
monero-project/research-lab #73 explains better
-
BigmenPixel[m]
Hello. Do I need to add the p2pool module for flatpak?
-
BigmenPixel[m]
-
selsta
BigmenPixel[m]: the problem is that the way p2pool is implemented it tries to install the binary in the same directory as the GUI
-
selsta
package managers don't like this
-
selsta
hyc: my gitian builds are running but will take a couple more hours, i don't have anything cached
-
BigmenPixel[m]
selsta: Then I can put the binary file there in advance?
-
selsta
might work
-
BigmenPixel[m]
selsta: Thanks.
-
hyc
selsta: ok
-
BigmenPixel[m]
<selsta> "might work" <- Sorry for stupid question.)) Is this p2pool necessary?:
-
BigmenPixel[m]
-
selsta
that's the software, yes
-
ooo123ooo123[m]
> <@bigmenpixel:matrix.org> Sorry for stupid question.)) Is this p2pool necessary?:
-
ooo123ooo123[m]
-
ooo123ooo123[m]
No
-
BigmenPixel[m]
🤔
-
selsta
is it 100% necessary to integrate in all distributions of monero-gui, no
-
BigmenPixel[m]
selsta: In flatpak, can’t integrate it manually without rebuilding, so it’s better to do it.
-
selsta
if you can easily integrate it then good, otherwise I'll add a compile time flag to disable p2pool for package managers
-
BigmenPixel[m]
selsta: Thank you for the second time. :)
-
merope
Btw, any chance that the rpc_pay feature gets "rewritten" to use p2pool instead of solo mining? As in, the client mines p2pool shares on behalf of the node, rather than full solo blocks
-
merope
Fits much better with the "small but consistent payouts" model
-
merope
(Perhaps point them directly to p2pool-mini even, rather than the main p2pool)
-
gingeropolous
wouldn't that require having p2pool in the daemon, or somehow routing the rpc_pay stuff to a p2pool daemon?
-
selsta
merope: the problem is that there is always incentive to run free of charge nodes for malicious actors, they need the data and not the hashrate
-
merope
oh I don't mean that as a solution for the malicious node problem, it was an unrelated suggestion about promoting rpc-pay
-
selsta
and as long as there are free nodes people are unlikely to use rpc-pay
-
ooo123ooo123[m]
<merope> "Fits much better with the "small..." <- p2pool is just an illusion of "small but consistent payouts"
-
merope
ooo123ooo123 not the place, and also wrong
-
selsta
what i meant, as it currently is i don't see rpc-pay being adopted
-
selsta
(even if it somehow uses p2pool)
-
merope
Right - but think of it in terms of "send a tip to your favourite public node to support them". Most people don't do that now, because the odds of finding anything are so low that it's not even worth their effort to figure it out
-
merope
But now that we have the p2pool integration, the odds of finding something on p2pool mini are significantly higher
-
ooo123ooo123[m]
merope: how much significantly in numbers ?
-
ooo123ooo123[m]
relatively to solo mining
-
merope
Main chain diff is ~300G these days, while p2pool mini typically hangs around 100M-200M
-
merope
so 1000x-3000x better odds of finding something
-
merope
Of course, the payout is proportional - but it's something
-
ooo123ooo123[m]
do you consider 1e-15 as something too ?
-
ooo123ooo123[m]
can you just use numbers instead of words ?
-
merope
Irrelevant question, but yes
-
ooo123ooo123[m]
they are ambigious
-
ooo123ooo123[m]
endor00[m]: There are no numbers in p2pool README too, only words "more frequent payouts"
-
ooo123ooo123[m]
Therefore it's an illusion
-
ooo123ooo123[m]
edit: it uses word "Regular"
-
UkoeHB
How do p2pool payouts compare to the differential fee from spending a p2pool output?
-
monerobull[m]
Fees are rather high, id say it's also rather easy to figure out the true sender
-
monerobull[m]
Since p2pool addresses are public, you could cross reference them with transactions that have tons of inputs. Unless your ring includes some other people miner address sending a large transaction it would be very easy to pinpoint you as the real sender, right?
-
monerobull[m]
s/people/p2pool/
-
ooo123ooo123[m]
<merope> "so 1000x-3000x better odds of..." <- Are you sure that 1000x-3000x multiplier is applicable to equal amount of "something" from pool mining / solo mining / p2pool mining ?
-
merope
Yes
-
ooo123ooo123[m]
merope: You're good at math then
-
ooo123ooo123[m]
<merope> "Yes" <- Can you help me to calculate it ? I believe it's at most 12x
-
ooo123ooo123[m]
relatively to solo mining
-
merope
This is not the right channel for this discussion
-
sethforprivacy
Do these cmake flags look correct for building static binaries?... (full message at
libera.ems.host/_matrix/media/r0/do…1c667cbd256e84b98ab4ebfb453ff86181a)
-
sethforprivacy
-
ooo123ooo123[m]
> <@sethforprivacy:matrix.optoutpod.com> Do these cmake flags look correct for building static binaries?... (full message at
libera.ems.host/_matrix/media/r0/do…0009cc9ee3d7497ce7c99252919e5a25949)
-
selsta
-
moneromooo
STATIC=ON will build most libs statically, if found.
-
moneromooo
Note "if found".
-
moneromooo
Though not giving you a static binary, pedantically.
-
sethforprivacy
Yeah, `file monerod` is still showing dynamically linked
-
sethforprivacy
I want a unified Dockerfile for multiple arches so depends is not ideal...
-
moneromooo
It's the best you're gonna get. Just make sure you don't have stuff you'd think should be static in ldd output.
-
sethforprivacy
Thanks
-
moneromooo
Like 0mq etc.
-
hyc
aren't all the dependencies in our depends builds static?
-
hyc
that's what gitian is for, setting up the env so nothing else is present
-
selsta
my daemon on master branch had a segfault but ulimit -c was set to 0 (even though it was set to unlimit from the last segfault..)
-
selsta
so I wasn't able to find a core file
-
selsta
have it running in gdb now
-
hyc
that's too bad. I've been running on master from (v0.17.0.0-67e5ca9ad) for ~9days now
-
selsta
so far all hashes match but still 3 operating systems to go to go
-
hyc
cool
-
hyc
if there were any timestamp discrepancies they'd certainly show up by now, anyway
-
selsta
btw all testnet node operators should compile master so that they end up on the correct chain
-
gingeropolous[m]
whens that fork?
-
hyc
less than a week\
-
plowsof[m]
Testnet hard-fork: May 16th, 2022, block 1982800 and 1983520
-
plowsof[m]
Stagenet hard-fork: July 9th
-
plowsof[m]
Mainnet hard-fork: July 16th, 2022, block 2668888
-
gingeropolous
ok, just compiled master and running testnet on xmrchain
-
sech1
hmm, need to spin up testnet p2pool by May 16th
-
gingeropolous[m]
lol cookie
-
sethforprivacy
Will it be tagged before then? I'll push a Docker build as well once there is a tag, or I can do a special one if not.
-
selsta
no tag
-
UkoeHB
selsta: what kind of time-line should I aim for with the 'good to haves' remaining here
monero-project/monero #8237 ?
-
selsta
I don't know, I don't see much point in not merging it just because some arbitrary dated passed.
-
selsta
The current multisig is broken anyway so as long as we didn't tag it should be fine.
-
UkoeHB
well it looks like you are wanting to tag in 5 days, when would the next tag be? or maybe I'm missing something
-
selsta
no we won't tag in 5 days
-
selsta
testnet hardfork doesn't require a tag
-
UkoeHB
stagenet then? 21 days?
-
UkoeHB
wait that's a month
-
selsta
yep
-
selsta
plan is to release ~1 month before mainnet hardfork
-
UkoeHB
ok I will try to get them PR'd by next monday
-
UkoeHB
or the first one anyway (and third one rebased)
-
UkoeHB
this coming monday*
-
monerobull[m]
this is about the ccs: i accidentally upvoted some ccs proposals with my gitlab github account eventhough i already upvoted them with my gitlab only account, I think i reverted everything but in case i missed one i wanted to make it clear that im not trying to manipulate any votes
-
selsta
.merge+ 8312
-
xmr-pr
Added