[ 3 / biz / cgl / ck / diy / fa / ic / jp / lit / sci / vr / vt ] [ index / top / reports ] [ become a patron ] [ status ]
2023-11: Warosu is now out of extended maintenance.

/biz/ - Business & Finance

View post   
File: 102 KB, 678x381, NANO-678x381.png [View same] [iqdb] [saucenao] [google]
8327006 No.8327006 [Reply] [Original]

Have you guys noticed that the output of the capacitors in the first layer of the "spend" frame for NANO have been a little volatile lately? I played around with them and starting changing the "exit values" to negative, or to really high positive (0-10 is normal, was doing 100 for example) and I found some strange occurrences. Anyone else look into this? Not really sure what it means but it could be related to the six sigmatic issue from prior to rebrand.

>> No.8327014

Sage.

>> No.8327023

>>8327006

Here's a reference point:

out_undo_partial_alloc:

while (--i >= 0) {

free_page((unsigned long)group_info->blocks[i]);

}

kfree(group_info);

return NULL;

}
EXPORT_SYMBOL(groups_alloc);

>> No.8327031

>>8327006
Keep Fucking around with it. Maybe you'll find some withdraw or depo glitch and you can find a way to multiply your nano.
I would suggest if you do manage to find a way, you exploit for a few days then let them know something fucked to get a bounty and move on with your life.

>> No.8327041

>>8327031

Do they currently have a bug bounty? I'm not even sure what the implications of this are, or if I've even found "something".

>> No.8327047
File: 203 KB, 802x854, 1500154415554.jpg [View same] [iqdb] [saucenao] [google]
8327047

the rumors have been flying all day about this. I have been poking at it from every angle with no luck Until I found it. I'll give you a hint - hook your api calls into the kernel library with a very large unsigned integer. The memory leak causes a buffer overflow allowing double-spend if you time it correctly. It requires some luck, in my testing I average 16% success rate. good luck out there anons.

>> No.8327048

>>8327006
I'm focusing on the nuclear kernel loop, currently separating the quantum layers with a laser coder injected in the main core

>> No.8327080

fucking stop with this horrible forced meme

>> No.8327081

>>8327014

No lol I wouldn't say I'm quite a sage, just a tech nerd. Thanks tho!

>> No.8327106

so the buffer overflow rumor is true.......

dear god

>> No.8327131

>>8327080
It's not even funny. At least the shadowfork Link meme was funny.

>> No.8327492

>>8327080
Triple spending is not a meme my friend, sorry for your bags friend.
If I was you I would sell before the main grid falls of the subledger.

>> No.8327787

>>8327492

AFAIK it's not the subledger that's the issue but the internal frame

>> No.8328185

You troll OP, but acyclic graph reversal on the receiving wallet, is a potential double spend vector. The receivers proof of work can be quasi-hashed and sent to the node, creating the allusion of funds never being received. However the funds have actually been siphoned through a separate node with a return to sender SIGTERM.
Both nodes will then broadcast the duplicate funds being held by the sender, while the receiver will hold a negative balance which can potentially be sent to any wallet, erasing legitimate funds.