00:08:11 <m-relay> <k​ayabanerve:matrix.org> geonic: So there are three currently defined milestones. You say at least include a deliverable. How are those milestones distinct?
00:08:37 <m-relay> <k​ayabanerve:matrix.org> Though I do hear your other suggested path, merging with any future work CCS.
05:13:42 <geonic> Unless I’m missing something, I don’t see any milestones in your proposal. How could there be milestones if it’s retroactive?
05:14:08 <geonic> “To be perfectly clear, in no uncertain terms, this CCS does not provide funding for nor guarantee any continued development. It is solely a representation of gratitude and acknowledgement for work already performed, and organization provided.”
05:15:06 <geonic> This is kinda problematic. Gratitude and acknowledgment are usually given once the work is done and/or functioning, not before
05:21:52 <geonic> The ccs as written puts the cart before the horse in multiple ways… my suggestions: 1) think about the deliverables 2) estimate the time required to produce the desired result 3) redact your proposal and let people decide if they want what you’re offering or not
05:30:24 <m-relay> <k​ayabanerve:matrix.org> geonic: there are three milestones, and CCS authors are explicitly allowed to work on milestones prior to funding.
05:30:34 <m-relay> <k​ayabanerve:matrix.org> There are no future milestones.
05:31:27 <geonic> I see 3 reasons it’s not ready for production, but I’m not seeing the milestones
05:31:57 <m-relay> <k​ayabanerve:matrix.org> As for deliverables, there is a FOSS codebase which does function. I'll agree it isn't complete, yet I'd appreciate if you stop ignoring its existence, and clarify what your definition of deliverables is. I assume you mean develivered into the m-p/m source tree?
05:32:11 <m-relay> <k​ayabanerve:matrix.org> View the CCS raw changes
05:32:38 <m-relay> <k​ayabanerve:matrix.org> I didn't include the metadata, which includes the milestones, in the description
05:32:38 <m-relay> <k​ayabanerve:matrix.org> I apologize if that's been confusing here
05:36:34 <m-relay> <k​ayabanerve:matrix.org> ... Yes, I definitely see how that'd cause this to read as no milestones. My mistake. First time submitting a CCS 😅
05:36:46 <geonic> one deliverable would be a paper outlining a clear path towards FCMPs under Seraphis
05:38:16 <geonic> another would be functioning code.. but I don’t know if that’s possible until Seraphis is up and running, at least on stagenet (not an expert, open to being corrected)
05:40:33 <m-relay> <k​ayabanerve:matrix.org> Current work has the exact API necessary on an academic level. Berman is working on integration.
05:41:10 <m-relay> <k​ayabanerve:matrix.org> So there's not necessarily a paper needed as the Seraphis paper defines the exact requirements, and this meets them.
05:41:52 <geonic> So why not wait until it’s integrated and you have something to show before asking for gifts to be brought to your feet
05:43:19 <geonic> Not sure about you, but I’ve never seen a good end to a conversation that started with “I want you to thank me” lol
05:45:04 <m-relay> <k​ayabanerve:matrix.org> For the reasons outlined in the post, that I believe it establishes its viability already. A further CCS on integration has already started. I'm talking with sarang about remaining protocol concerns and will resolve the ones raised in the current work. For future work, which I do acknowledge, I'd rather an appropriately sized CCS rather than an extra large one tying old work with future work.
05:45:41 <m-relay> <k​ayabanerve:matrix.org> With this separation, the community can decide against retroactive funding, and it won't also tank my proposal for future work.
05:46:13 <m-relay> <k​ayabanerve:matrix.org> I could wait till post mainnet deployment, sure but I don't want to request funding 1-2y after the fact :/
05:47:16 <geonic> do you expect to bring your work on FCMPs to completion with the next CCS or do you foresee more than one proposal?
05:48:18 <m-relay> <k​ayabanerve:matrix.org> I'd personally rather do proposals regarding a few months of work at a time, than monolithic ones.
05:48:23 <geonic> Or let me phrase it this way… what will be the deliverables at the end of the next CCS?
05:48:42 <m-relay> <k​ayabanerve:matrix.org> I haven't scoped out the exact hours remaining on the current issue board.
05:49:27 <m-relay> <k​ayabanerve:matrix.org> I'd assume a productionized implementation of the current code. That'd partner with Berman's integration work and get us something deployable, once audited.
05:49:50 <m-relay> <k​ayabanerve:matrix.org> Though it may not necessarily be complete. There's always a lot of optional nooks and crannies...
05:51:23 <geonic> Ok.. and all of your work is dependent on whether the project decides to move to curve cycle?
05:51:45 <geonic> I see that as step 5 under “What’s next”
05:52:03 <m-relay> <k​ayabanerve:matrix.org> Technically not, though not doing so would remain one of the stupidest decisions Monero could make IMO
05:52:47 <geonic> So your work is viable even if we don’t? Why is it a step in the process?
05:52:57 <m-relay> <k​ayabanerve:matrix.org> We have a tower cycle which would 4x proof size and reduce performance, yet would work.
05:53:11 <m-relay> <k​ayabanerve:matrix.org> Because we'd be idiots not to
05:53:29 <m-relay> <k​ayabanerve:matrix.org> And if we don't do so, we need to implement 3 new elliptic curves
05:55:06 <m-relay> <k​ayabanerve:matrix.org> TBC, a curve cycle isn't just for FCMPs. They enable logarithmic IVC, without a trusted setup, and have many reasons for them.
05:55:35 <m-relay> <k​ayabanerve:matrix.org> But without them, which I truly believe will nuke Monero's scalability, FCMPs also suffer.
05:55:57 <m-relay> <k​ayabanerve:matrix.org> Er, sorry, 2x proof size, ~1.7x proof time.
05:56:21 <m-relay> <k​ayabanerve:matrix.org> So next step is either curve cycle or tower cycle. The former is just the same next step.
05:58:18 <m-relay> <k​ayabanerve:matrix.org> *sane next step
05:59:21 <geonic> That’s all above my pay grade.. thanks for answering. Hopefully luigi makes a decision soon so you can move on.
05:59:23 <geonic> cheers
06:37:24 <m-relay> <1​23bob123:matrix.org> community*
14:00:09 <m-relay> <b​iologe2:matrix.org> Greetings. I sent a transaction to the GUI wallet, but it hasn't arrived for almost two days. There are more than 100 confirmations. How can I fix it? Help me please.
14:03:40 <m-relay> <b​iologe2:matrix.org> The address is entered correctly. Checked many times
14:08:22 <dEBRUYNE> Can you verify the transaction first? https://monero.stackexchange.com/revisions/6138/1
14:50:13 <m-relay> <b​iologe2:matrix.org> I can't
14:51:55 <m-relay> <b​iologe2:matrix.org> Help me please.
15:05:03 <kico> biologe2, is your node fully synced?
15:05:19 <kico> remote or local?
15:06:43 <m-relay> <b​iologe2:matrix.org> Yes
15:06:53 <m-relay> <b​iologe2:matrix.org> Local
15:07:06 <kico> is it fully synced?
15:07:34 <kico> are you windows or linux?
15:07:49 <m-relay> <b​iologe2:matrix.org> Yes
15:08:02 <m-relay> <b​iologe2:matrix.org> Windows 10
15:08:18 <kico> ok not sure this will work on windows
15:08:34 <kico> try on your browser http://127.0.0.1:18081/getinfo
15:08:40 <m-relay> <b​iologe2:matrix.org> tried reinstalling - didn't help
15:08:46 <kico> what's your height?
15:09:32 <kico> .network
15:09:33 <m-relay> <b​iologe2:matrix.org> I did not understand the question
15:09:36 <kico> oh le bux is ded
15:09:50 <m-relay> <p​lowsof:matrix.org> biologe2 settings>wallet>info what wallet mode? If simple , read this comment
15:09:51 <kico> try to copy paste this on your browser http://127.0.0.1:18081/getinfo
15:10:20 <m-relay> <p​lowsof:matrix.org> https://github.com/monero-project/monero-gui/issues/4127#issuecomment-1465055249
15:11:05 <m-relay> <b​iologe2:matrix.org> simple mode
15:11:21 <m-relay> <p​lowsof:matrix.org> To get to change wallet mode you probably have to close the open wallet first. Top left corner.. looks like [<-
15:11:26 <kico> yeah you're probably not fully synced
15:12:16 <m-relay> <b​iologe2:matrix.org> did
15:13:58 <m-relay> <b​iologe2:matrix.org> When entering the wallet, it says that "Synchronization". It ends in a few minutes. Coins do not appear\
15:15:48 <m-relay> <b​iologe2:matrix.org> I got out of the box. What to do next?
15:16:42 <kico> try a remote node like plowsof said
15:16:59 <m-relay> <b​iologe2:matrix.org> Everything was fine before, with other wallets. And with this something went wrong, although I did not change any settings
15:17:19 <kico> but you reinstalled
15:17:23 <kico> just try it man
15:17:29 <m-relay> <p​lowsof:matrix.org> Once wallet mode is advanced. Select open wallet from fille. Then follow instructions from fhe github comment. Let me know when that done
15:18:57 <m-relay> <p​lowsof:matrix.org> Have you told us your wallet version biologe2? (Also in settings>info>wallet) can better move this to #monero-support:monero.social
15:21:39 <m-relay> <b​iologe2:matrix.org> 0.18.2.2-unknown (Qt 5.15.8)
15:34:33 <m-relay> <b​iologe2:matrix.org> https://matrix.monero.social/_matrix/media/v1/download/matrix.org/RPaMxyZIARucahaKQYEEiZRt
15:34:54 <m-relay> <b​iologe2:matrix.org> Do I need to wait until "Synchronization" ends and the problem is solved?
15:46:38 <kico> biologe2, yeah if it remains after sync come back
15:46:53 <kico> that's the most likely cause
15:47:08 <m-relay> <p​lowsof:matrix.org> Biologe2 click remote node. Then (+) add remote node. Ip / port in the github comment
15:47:51 <m-relay> <p​lowsof:matrix.org> After adding the node, click on it so its highlighted grey and it will begin syncing
15:48:59 <kico> if he wants to run a remote node otherwise he should let his node sync?
15:54:58 <m-relay> <p​lowsof:matrix.org> True kico, but depending on their system specs we may not be here to help when its finished :(
15:55:27 <kico> plowsof, lol fair point
15:55:45 <kico> also maybe he doesn't even have enough storage for the chain
15:56:16 <kico> biologe2, do you have enough diskspace to have a full copy of the blockchain localy?
15:56:46 <kico> make sure you want to run a full node first
15:56:52 <kico> otherwise just use a remote one :)
15:57:06 <m-relay> <b​iologe2:matrix.org> I have somewhere 50 gigabytes free
15:57:59 <kico> it's not enough sir
15:58:08 <kico> you need ... 140gbs (?)
15:58:22 <kico> for full node if pruned maybe 70GBs (?)
15:58:42 <kico> so yeah plowsof is right
15:58:57 <kico> biologe2, try a remote node
15:59:25 <kico> like address: node.community.rino.io port: 18081
15:59:30 <kico> and let it sync
15:59:34 <kico> report back later
16:00:28 <m-relay> <s​needlewoods_xmr:matrix.org> my data.mdb  is currently ~ 176gb
16:01:40 <m-relay> <s​needlewoods_xmr:matrix.org> luckily 500gb ssd is quite cheap nowadays
17:19:15 <m-relay> <b​iologe2:matrix.org> image.png
17:19:55 <m-relay> <b​iologe2:matrix.org> Did not work out
17:22:44 <m-relay> <b​iologe2:matrix.org> image.png
17:28:31 <m-relay> <p​lowsof:matrix.org> Biologe2 what version wallet ? Settings>info>wallet
17:28:52 <m-relay> <b​iologe2:matrix.org> 0.18.2.2-unknown (Qt 5.15.8)
17:31:59 <m-relay> <p​lowsof:matrix.org> And you can see the text print out of rinos node if you look in your browser http://node.community.rino.io:18081/get_info ?
17:32:05 <m-relay> <b​iologe2:matrix.org> {
17:32:05 <m-relay> <b​iologe2:matrix.org>   "adjusted_time": 1693934168,
17:32:06 <m-relay> <b​iologe2:matrix.org>   "alt_blocks_count": 0,
17:32:06 <m-relay> <b​iologe2:matrix.org>   "block_size_limit": 600000,
17:32:07 <m-relay> <b​iologe2:matrix.org>   "block_size_median": 300000,
17:32:07 <m-relay> <b​iologe2:matrix.org>   "block_weight_limit": 600000,
17:32:08 <m-relay> <b​iologe2:matrix.org>   "block_weight_median": 300000,
17:32:08 <m-relay> <b​iologe2:matrix.org>   "bootstrap_daemon_address": "",
17:32:09 <m-relay> <b​iologe2:matrix.org>   "busy_syncing": false,
17:32:09 <m-relay> <b​iologe2:matrix.org>   "credits": 0,
17:32:10 <m-relay> <b​iologe2:matrix.org>   "cumulative_difficulty": 302844866839386274,
17:32:10 <m-relay> <b​iologe2:matrix.org>   "cumulative_difficulty_top64": 0,
17:32:11 <m-relay> <b​iologe2:matrix.org>   "database_size": 268435456000,
17:32:11 <m-relay> <b​iologe2:matrix.org>   "difficulty": 252802919946,
17:32:12 <m-relay> <b​iologe2:matrix.org>   "difficulty_top64": 0,
17:32:12 <m-relay> <b​iologe2:matrix.org>   "free_space": 18446744073709551615,
17:32:13 <m-relay> <b​iologe2:matrix.org>   "grey_peerlist_size": 0,
17:32:13 <m-relay> <b​iologe2:matrix.org>   "height": 2967654,
17:32:55 <m-relay> <p​lowsof:matrix.org> Did you select close daemon earlier? (Not leave it running?)
17:33:52 <m-relay> <b​iologe2:matrix.org> Didn't understand what to do
17:33:54 <m-relay> <p​lowsof:matrix.org> Turn your computer on and off again
17:34:36 <m-relay> <b​iologe2:matrix.org> Unfortunately I do not understand((
17:36:48 <m-relay> <p​lowsof:matrix.org> Its ok, close the gui, computer off / on , then open the gui again for round 2
17:37:49 <m-relay> <p​lowsof:matrix.org> Please go to #monero-support:monero.social
17:45:39 <m-relay> <b​iologe2:matrix.org> I rebooted. Nothing changed
17:50:45 <m-relay> <b​iologe2:matrix.org> image.png
17:54:30 <m-relay> <s​iren:kernal.eu> https://monerodevs.org should look like this https://www.lightning-landscape.net
17:54:46 <m-relay> <r​ucknium:monero.social> biologe2: It's working fine. Syncing can take hours. The progress bar in the lower left looks like it is moving. Watch "wallet blocks remaining"
17:56:34 <m-relay> <r​ucknium:monero.social> If you are restoring the wallet from seed, I hope you set the restore height/date correctly
17:57:11 <m-relay> <b​iologe2:matrix.org> photo_2023-09-05_20-56-16.jpg
17:57:12 <m-relay> <b​iologe2:matrix.org> syncing at the moment?
17:57:22 <m-relay> <r​ucknium:monero.social> At your current restore height, you will definitely find the recent transaction(s). But if you have a really old transactions, it might not find them.
17:58:20 <m-relay> <r​ucknium:monero.social> Wallet blocks remaining is lower than the last image you posted, so 90% sure yes
18:00:11 -xmr-pr- [meta] Rucknium opened issue #890: Monero Research Lab Meeting - Wed 06 September 2023, 17:00 UTC
18:00:11 -xmr-pr- > https://github.com/monero-project/meta/issues/890
18:01:38 <m-relay> <b​iologe2:matrix.org> For some reason, everything dropped
18:02:06 <m-relay> <b​iologe2:matrix.org> https://matrix.monero.social/_matrix/media/v1/download/matrix.org/nJKamYKrIaeYEnNzogPhyoir
18:12:40 <m-relay> <b​iologe2:matrix.org> I understand correctly that this strip must reach the end? Until she reaches nothing to press?
18:13:11 <m-relay> <b​iologe2:matrix.org> https://matrix.monero.social/_matrix/media/v1/download/matrix.org/oFihauZoqEZfbsNZmytXkWWH
18:15:03 <m-relay> <r​ucknium:monero.social> It has to sync. The progress bar must go full, all the way to the right
19:45:11 -xmr-pr- [meta] umma08 opened issue #891: Monero Policy Working Group Meeting: Tuesday 3rd October @ 16:00 UTC
19:45:11 -xmr-pr- > https://github.com/monero-project/meta/issues/891
19:45:22 <m-relay> <c​hch3003:monero.social> I just want to say thank you y'all for your work :) Stay happy, stay fresh, stay healthy. We will win.
21:38:23 <m-relay> <s​hadow:simplifiedprivacy.is> Monero Wallets: Which is Right For You?
21:38:23 <m-relay> <s​hadow:simplifiedprivacy.is> https://simplifiedprivacy.com/monero-wallets-which-is-right-for-you/