Topic: [ANN] Ravencoin [RVN] PoW GPU Mining | Asset Transfer Blockchain (Updated ANN) - page 3. (Read 1170621 times)

Dev Meeting Transcripts (April, 2022)

[4:00 PM] kinkajou (SegWit Clique): Channel open
[4:03 PM] Tron: Thanks kinkajou (SegWit Clique) for opening the channel each week.
[4:05 PM] Tron: I'm still working on the 6 failing tests.   It is related to the P2SH changes, and the IsStandardTx function.  I can easily fix the tests to not error, but I want to understand the ramifications of IsStandardTx function failing before making changes.
[4:07 PM] Tron: 1 of the tests is failing as "dust", and the other with "scriptpubkey".  It might be as simple as adding a type for P2SH, but that might also have knock-on effects to allow a transaction type that we shouldn't allow.
[4:08 PM] Tron: These are the tests that are failing:
[4:08 PM] Tron: feature_fee_estimation.py
feature_maxuploadtarget.py
mempool_limit.py
mining_prioritisetransaction.py
wallet_basic.py
rpc_addressindex.py
[4:13 PM] kinkajou (SegWit Clique): Same failures myself and ilaypipe got.
Can we look at merging 1184 to develop if it has been reviewed? https://github.com/RavenProject/Ravencoin/pull/1184#issuecomment-1076532365
It seems to be the source of a lot of issues on the testnet
[4:14 PM] kinkajou (SegWit Clique): There's also been some talk about adding kralverde 🤡 🇺🇸 as a core developer in ravenqt-sig-working perhaps he should have permissions?
[4:14 PM] Hans_Schmidt: FYI, I changed the way nonstandard txns work on testnet in PR#1048.
Previously, the chains rejected nonstandard transactions according to=> mainnet:true, testnet:false, regtest:false
The "-acceptnonstdtxn" CLI switch option was broken and had no effect.
After the PR, all chains default to rejecting nonstandard transactions, while allowing the "-acceptnonstdtxn" switch to change that behavior on testnet and regtest (but not mainnet).
[4:40 PM] LSJI07: One dev meeting starts and suddenly there is like a few new miners on testnet. Welcome! 😋
[4:42 PM] Tron: Merged 1184
[4:44 PM] Hans_Schmidt: Thanks!
[5:40 PM] kinkajou (SegWit Clique): I'll go ahead and close the channel then. Thanks everyone for coming!
-------------------------------------
[4:00 PM] BadGuyTy: yay
[4:00 PM] kinkajou (SegWit Clique): Hello, channel should be open.
[4:01 PM] BadGuyTy: ok whats the stats of the bugs I want this release out the door so I can push through the mineable assets
[4:02 PM] BadGuyTy: How much C++ am I going to have to learn to get this done?
[4:03 PM] Someone_2: well there's also the hash header bug or whatever they're call it that was come across.
[4:03 PM] Someone_2: it was snagged/discovered on the testnet
[4:03 PM] BadGuyTy: I had to go dig through java earlier this week to find a stupid setting because the local devs couldn't be bothered to figure out the issue them selves
[4:04 PM] Someone_2: kind of a recap of last weeks meeting, Tron's invstigating why the python tests failed and wanted to investigate it further because it involves consensus code.
[4:06 PM] Tron: Quite a bit.  Also a good understanding of the format of the coinbase, tranasactions, and the UTXO model.  Also, some python to add functional tests.
[4:06 PM] LSJI07: Hi.
[4:07 PM] BadGuyTy: I got python down
[4:07 PM] Tron: Still working on the tests.  Last week was very busy.
[4:07 PM] BadGuyTy: yeah I had to actually go into the office 😲  this week
[4:07 PM] Tron: The Blockchain Law Alliance site launched: https://roundtable.io/blockchain-law-alliance/
Blockchain Law Alliance
Blockchain Law Alliance
News and thoughtful analysis on blockchain regulations and their impact.
[4:08 PM] BadGuyTy: nice we need some sensible laws
[4:09 PM] Tron: We should be able to get it in front of a few US Senators (Lummis, and Lee at a minimum).
[4:10 PM] BadGuyTy: the other day Romney tried to tell me crypto was still a tool for criminals 🤦
[4:12 PM] kinkajou (SegWit Clique): Crypto is for everyone.
[4:12 PM] Tron: Point him to this site.  It will help correct these types of misunderstandings.
[4:13 PM] Tron: Utah is in pretty good shape for crypto.  There's already discussion of being able to pay for state services and taxes in crypto. It's some of the other states' Senators that need more education.
[4:13 PM] BadGuyTy: Anyways so to get this release out the door we need to figure out why those 6 python tests were failing
[4:14 PM] Tron: I'm on the Executive Board of the recently formed Utah Blockchain Coalition.  https://www.utahblockchain.org/
www.utahblockchain.org
piperhillconsulting
Home Page | www.utahblockchain.org
Utah Blockchain Coalition. A collective of industry partners and individuals working together to establish Utah as a leader in Blockchain and Cryptocurrency. About Utah Blockchain Coalition The Utah Blockchain Coalition is a collective of industry partners and individuals working together to est ...
[4:15 PM] BadGuyTy: I'm not good at coding  (non python languages) but finding bugs and digging through code I do well
[4:15 PM] Someone_2: any news on the header hash issue on testnet?  I know people have been using the invalid and reconsier commands.  I never got it to work, kept crapping out.
[4:16 PM] Someone_2: (maybe it's fixed and I don't know about it 🙂
[4:17 PM] kinkajou (SegWit Clique): Are you running Hans' 4.8 release?
[4:18 PM] Someone_2: I am not , no.  Haven't tried synching anything testnet in at least a week.
[4:19 PM] Someone_2: I had orignially set out to try doing the DPI scaling test as I see it as something I can do without knowing how to code and it would be an item to finally knock off the list.  Never got the testnet client to synch.
[4:21 PM] kinkajou (SegWit Clique): https://github.com/RavenProject/Ravencoin/issues/1188
Have you tried the
invalidateblock reconsiderblock
 described here?
[4:22 PM] Tron: If anyone has node IP addresses for the testnet, could you put them here?
[4:22 PM] Someone_2: Yep tried the invalidate block and reconsider, it didn't work, tried it 4 times.  I was not aware a new testnet client was out.
[4:23 PM] Someone_2: Kalverde quasi walked me through trying it.
[4:24 PM] kinkajou (SegWit Clique): Hans' new release can be found here: https://github.com/hans-schmidt/Ravencoin/releases/tag/v4.8.0test1
[4:25 PM] Someone_2: will give it a try 🙂
[4:39 PM] Hans_Schmidt: The 4.8 version does not contain a fix for the block #1127354 issue on testnet. In practice, a lot of people have been finding that 4.8 doesn't fail purely because it is statically linked, and they were previously using a client which they built themselves with dynamic linking (which appears to fail much more often). I spent some time looking at this issue, but it looks like a really flaky race condition. And testnet has been so inconsistently mined that it's often hard to tell which issues are specific to testnet. I ended up putting this on the back burner for a while.
[4:42 PM] Someone_2: I'll still try it out.  Will see how it goes.
[4:43 PM] Hans_Schmidt: I just pick the best ones from here: https://rvnt.cryptoscope.io/network/
[4:56 PM] kinkajou (SegWit Clique): I will see if I can work out a long-term fix for the testnet mining issue this week then.
-------------------------------------
[4:00 PM] kinkajou (SegWit Clique): Channel open
[4:06 PM] kinkajou (SegWit Clique): Tron any progress on those 6 failing tests?
[4:14 PM] Tron: Some.  I recalled having the tests pass for p2sh and requesting another test or two for a failed multisig. I started with master and pulled in the original P2SH changes (commit 8c31e2b6c5668b6e59db0ed5375db1c1b017bedc) and the tests pass. Somewhere along the way, the test broke.  Next step -- find out where/when.
-------------------------------------
[4:00 PM] kinkajou (SegWit Clique): 👋
[4:17 PM] Sevvy ♾ (werebear): Heya
[4:17 PM] LSJI07: Hi
[4:17 PM] Steelers: 👋
[4:18 PM] Hans_Schmidt: Yo
[4:20 PM] LSJI07: What's the priority at the moment? Anything we can help with?
[4:21 PM] Hans_Schmidt: Testing on testnet
I spent a half-day this week back-and-forth with BF diagnosing and developing a patch for the Testnet Block #1127354 Sync Hang Bug
We believe that this fixes the bug. But the intermittent nature of the bug makes additional testing necessary.
Pre-compiled binaries including this PR for use on testnet testing are available at
https://github.com/hans-schmidt/Ravencoin/releases/tag/v4.8.5test1
The bug is related to the use of SubQualifiers for Restricted Assets and exists in all previous versions of core which support Restricted Assets. Since it is a failure in reading cache properly, it does not occur once the cache flushes to database, making it dependent on node speed, compile types, and other things which affect timing.
[5:55 PM] kralverde 🤡 🇺🇸: I'll move my mining node over
-------------------------------------
[4:00 PM] kinkajou (SegWit Clique): Channel open
[4:03 PM] kinkajou (SegWit Clique): Tron any more progress made on those failing tests?
[4:04 PM] Tron: I haven't had much time.  I have found one specific PR that adds 3 failures -- so narrowing it down.
[4:04 PM] Tron: Sorry I missed last week's dev meeting.  I was speaking at the Utah Bitcoin Conference.
[4:05 PM] kinkajou (SegWit Clique): Which PR is it?
[4:09 PM] Tron: 8c31e2b6c5668b6e59db0ed5375db1c1b017bedc
[4:10 PM] Tron: feature_assets_p2sh.py                                                  | ✖ Failed  | 2 s
[4:11 PM] Tron: Second test run only gave 2 failures.  1 of the failures may have been a connection failure.
[4:13 PM] Tron: Has anyone experienced sync failures using:  Pre-compiled binaries including this PR for use on testnet testing are available at
https://github.com/hans-schmidt/Ravencoin/releases/tag/v4.8.5test1 ?
[4:15 PM] Someone_2: I had been specifically having synch problems repeatedly.  The one at the above link seems to have fixed it.  Synched no problem at all on the firs try.
[4:16 PM] kinkajou (SegWit Clique): I'll test that release Monday but I wasn't having sync issues with the previous 2 releases. Core Tester did any of you get a chance to look at it this week?
[4:23 PM] LSJI07: I haven't tested that.
[4:28 PM] LSJI07: Downloaded and syncing now.
[4:30 PM] LSJI07: Partial syncing now. After that will try a full sync.
[4:40 PM] LSJI07: the last 3 weeks is taking a while. 10 nodes connected, zero banned.
[4:59 PM] Mango Farm: No sync issues with 4.8.5 on my end but have had unexplained crashes on windows when solo mining testnet for multiple versions.  Can’t say what the cause is.  The miner continues to run so it is on the Raven side but the log reports only show GUI errors.
[5:03 PM] LSJI07: Are you still getting crashes on 4.8.5 specifically? I understood that had a fix for mining rapid blocks in succession.
[5:05 PM] Mango Farm: Yes.  At startup 4.8.5 will mine a ton of blocks quickly until the difficulty adjusts but after about a day I’ll notice it is shut down (with the miner and windows still running).  The log shows gui errors but that’s it.  I have it up now so will drop the log when it replicates again.
[5:08 PM] LSJI07: my node is claiming the partial sync will finish in 10 mins. ill redo a full sync after the partial finishes.
[5:09 PM] Hans_Schmidt: The mining bug which we fixed did not crash core. It locked up core in a continuous loop which you couldn't get out of without killing core. But it required a VERY specific set of circumstances.
[5:11 PM] Mango Farm:
Image
[5:13 PM] Mango Farm: There’s the last log before a crash but I wasn’t very methodical about being certain that was the last thing.  I’ll keep an eye on it and wait for a crash.  Then post with more certainty.  It’s not a 4.8.5 issue it has been happening for a while.  I thought it was windows sleeping but this last go I learned that was not it.
[5:14 PM] Hans_Schmidt: Never seen that one before. You say multiple versions? Do you know if that includes v4.3.2.1 or only newer versions?
[5:15 PM] Mango Farm: Only post 4.3.2.1.  And only windows.  I have post 4.3.2.1 testnet linux nodes running without issue.
[5:16 PM] Mango Farm: I’ll see if I can narrow this down and produce a log I’m sure immediately preceded the crash next time it does it.  Mind you I’m solo mining on this node so that could be a unique factor at play.
[5:18 PM] Hans_Schmidt: Which miner are you using (so I can try to duplicate)? TTMiner?
[5:18 PM] Mango Farm: Tt
[5:19 PM] Mango Farm: Windows 10 home is the OS
[5:20 PM] Hans_Schmidt: With all those GUI errors and Windows only, it might be QT related since we did a lot of QT upgrade work since v4.3.2.1. The QT in v4.3.2.1 was dangerously old. The upgrade fixed multiple QT security issues, but a number of projects have reported other new bugs.
[5:24 PM] LSJI07: Partial sync completed fine on 4.8.5test1. Doing the full sync now.
[5:25 PM] LSJI07: Only 3 years and 31 weeks to go.
[5:25 PM] Mango Farm: I tested the sync on 4.8.5 several times and it worked like a charm
[5:28 PM] Hans_Schmidt: v4.8.5test1 seems to have fixed the SubQualifier sync hang bug for me too. I think we killed that bug.

Reminder: RVN mod Seal Clubber is a crypto scammer, and more people involved as well.

https://imgur.com/a/IUYYLM4
mirror:
https://ibb.co/SVLLFh2
https://ibb.co/gyZZYm2

Currently, its #4, after ETH, ETC and FIRO

Some miners are strange. I don't understand why some people get hung up on particular coins and can't move past them.

Where are you looking to see that RVN is usually top 3 profitable? On Whattomine it's rarely a top 10 profitable coin.

People even mine Ubiq and Expanse, although profirability is close to zero.
RVN is usually in top 3 profitable

I would argue that miners will mine whatever is most profitable, but this shitcoin consistently proves that wrong. I can't wrap my head around why people continue to mine less profitable coins.

ETC and Ergo yes, but Conflux is way way worse

Miners aren't gonna switch to this as main POW coin. The Algo is power hungry pos. ETC/Ergo/Conflux are all beating this dead coin.

Miners will be happy to see some price movement for the coin for when ETH goes full POS. Other than having something to mine and sell there isn't much going for this shitcoin.

It will be interesting to watch the price once ETH is no longer minable. I would expect a ton of downward price pressure as miners look to mine and sell this shitcoin.

keep the pump and dump alive ppl LOLLL

Dev Meeting Transcripts (March 2022)

[4:00 PM] kinkajou (SegWit Clique): Channel open
[4:02 PM] Tron: Listening to a Twitter Spaces related to tZero (https://twitter.com/RavenRickGrime1/status/1499851118540558337)
[4:17 PM] Someone_2: I'm around but happen to be building a computer.
[4:39 PM] Hans_Schmidt: Has anyone tried to run the python functional tests against the develop branch? It appears to be failing 5 tests. I haven't had time to diagnose yet.
[4:47 PM] kinkajou (SegWit Clique): I have not done any testing since Fdov put out the call for volunteers on the test3 binaries. Do you have a link?
[4:52 PM] Hans_Schmidt: The procedure is documented at https://github.com/RavenProject/Ravencoin/blob/master/test/README.md Run the whole test_runner.py testset
[12:05 AM] Tron: I'm out-of-network-range tomorrow (Fri).
----------
[4:00 PM] kinkajou (SegWit Clique): Channel open
[4:03 PM] burix: Hi. I would like to know if there's an ETA for p2sh and if not, let's make one? referencing Hans' msg from here: https://discord.com/channels/429127343165145089/482289959261175838/931673484772376606
[4:05 PM] BadGuyTy: I think we just need to bite the bullet and get it out there unless there is some compelling reason to get more tested than what is currently tested
[4:06 PM] kinkajou (SegWit Clique): Has anyone run the integration tests and replicated the errors Hans' described last week?
[4:07 PM] BadGuyTy: I forgot i missed last week and didn't read all the comments well then we would need to solve those first.
[4:25 PM] kinkajou (SegWit Clique): u/Hans_Schmidt is that the only thing holding up release? I can take a look at it this weekend and post an announcement for volunteer testers.
[4:32 PM] Hans_Schmidt: Those 5 functional test failures, a few remaining PR approvals (ie the fix for the bug which crashed miners- I shouldn't approve my own patch code), and some tests which Tron requested at https://discord.com/channels/429127343165145089/482289959261175838/944344833110192178
----------
[4:00 PM] kinkajou (SegWit Clique): Channel open!
[4:03 PM] kinkajou (SegWit Clique): Hans_Schmidt I ran the functional tests and got 6 failures, so 1 more than expected.
feature_fee_estimation
feature_maxuploadtarget
mempool_limit
mining_prioritisetransaction
rpc_addressindex
wallet_basic
[4:07 PM] kralverde 🤡 🇺🇸: I also found some errors while syncing from scratch having to do with tagging addresses with sub qualifiers on testnet
[4:08 PM] kralverde 🤡 🇺🇸: Ill need to try and dig into the code to see whats up
[4:13 PM] Tron: I can take a look at the tests this week.
[4:16 PM] Tron: The reason for sub-qualifiers is so KYC in the token rule would work KYC/PROVIDER_A and KYC/PROVIDER_B
[4:17 PM] Tron: If it has changed AND we decide we want it changed, then it will need to be wrapped in BIP9
[4:18 PM] kralverde 🤡 🇺🇸: Right, but theres something on the testnet chain right now that is choking up syncing
[4:18 PM] kralverde 🤡 🇺🇸: Should be valid but the (new) nodes dont like it
[4:19 PM] Someone_2: Hmm, I'm synching right now, was goign to try my hand at the DPI scaling testing.  Will keep an eye on it.
[4:20 PM] kralverde 🤡 🇺🇸: Should be around 1270000
[4:21 PM] kralverde 🤡 🇺🇸: Actually i can look it up rn
[4:21 PM] kralverde 🤡 🇺🇸: 1127354
[4:22 PM] Someone_2: I"m still on the headers.  Probably won't get to the blocks til tomorrow.
[4:23 PM] Someone_2: will keep an eye on it.
[4:23 PM] kralverde 🤡 🇺🇸: Cool ty
[4:23 PM] Someone_2: You've got me wondering what will happen 🙂
[4:24 PM] Someone_2: I plan to just leave it on and let it run straight through.
----------
[4:00 PM] kinkajou (SegWit Clique): Channel open
[4:02 PM] Nonprophete: I'll start with the usual, when P2SH?
[4:02 PM] kinkajou (SegWit Clique): Tron did you get a chance to look at those failing tests this week?
[4:03 PM] Nonprophete: Also, any ETA on when work will being on this?  Phase 7 - Compatibility Mode
Allows newly created assets to appear exactly like RVN, LTC, or Bitcoin for easy integration into exchanges, wallets, explorers, etc. Speeds adoption into the larger crypto ecosystem.
[4:03 PM] Tron: I'm still working on it.  I'm reconstructing the dev environment on my Mac (via Parallels) because my PC died.
[4:08 PM] Tron: I don't know how much value the compatibility mode has - now.  At the time it was proposed, most coins were Litecoin-like.  Now most tokens are Uniswap-like.  There might be more value in mimicking ERC-20 - only possible if exchanges are not monitoring the Ethereum chain directly.  Or building an abstraction layer like Rosetta.
[4:13 PM] kinkajou (SegWit Clique): How would that look relative to a UTXO implementation? I only have a rudimentary understanding but it seems to me like mimicking LTC/BTC would be much easier and probably more secure since assets already transact similar to those chains.
[4:14 PM] Tron: It is easier, but so far there isn't demand for that compatibility layer.
[4:14 PM] Nonprophete: Fair enough.  It should probably be removed from the roadmap until a decision can be made.
[4:15 PM] Tron: PERPER might want something like that if there are exchanges that are wired for Bitcoin, Litecoin, etc.  But some of those (like Coinbase) use an abstraction layer like Rosetta anyway.
[4:16 PM] kinkajou (SegWit Clique): So something similar to a "wrapped asset"? Would we then need a sort of Ravencoin-Asset specific smart-contract standard?
And Rosetta would be what we already did for RVN as part of the coinbase listing requirements but expanded to include assets? or is there more needed?
[4:17 PM] Tron: Agreed.  We could just mark it as deprecated (on the road map).
[4:21 PM] Hans_Schmidt: There were some problems this week on testnet during restricted asset testing which caused some nodes to stop sync'ing. Initially it was thought that the newest develop branch was to blame. But now it appears that it may be a race condition which is worse on non-statically-liked binaries of core. It is not yet known whether v4.3.2.1 also has this problem. It doesn't want to fail while running in a debugger. In any case, it would be best if people ran the latest version of "develop" on testnet so that we can continue testing what will get released.
For convenience for people who don't want to build their own statically-linked binaries, I have posted the latest "develop" code for all platforms except Mac at:
https://github.com/hans-schmidt/Ravencoin/releases/tag/v4.8.0test1
[4:39 PM] kralverde 🤡 🇺🇸: For testing, it would be best to specifically deny an address with a qualifier but allow it with a sub qualifier.  Then send a restricted asset to that address
[4:40 PM] kralverde 🤡 🇺🇸: I havent delved into the code, but could it be a fail fast condition?
[4:41 PM] kinkajou (SegWit Clique): Core Tester if any of you are available to test this week. What is the expected behavior kralverde 🤡 🇺🇸 ?
[4:41 PM] kralverde 🤡 🇺🇸: Everyones testnet node will stop syncing lol
[4:41 PM] kralverde 🤡 🇺🇸: Well a good portion
[4:42 PM] kralverde 🤡 🇺🇸: Assuming theres only one miner
[4:42 PM] kralverde 🤡 🇺🇸: It may be overwritten now that theres more
[4:42 PM] kralverde 🤡 🇺🇸: Just keep logs open
[4:42 PM] ilaypipe: If I get a guide I can dedicate some time to testing after work
[4:42 PM] kinkajou (SegWit Clique): Syncing my testnet node built from develop branch now.
[4:42 PM] kinkajou (SegWit Clique): I can help you after I look into it myself.
[4:43 PM] kralverde 🤡 🇺🇸: Itll likely be a “dropped node misbehaving” error
[4:46 PM] Hans_Schmidt: kralverde 🤡 🇺🇸 put a good overview of the problem at https://github.com/RavenProject/Ravencoin/issues/1188
[4:51 PM] Hans_Schmidt: For me, an immediate "reconsiderblock" of the failing block restarts the sync with no need to do any "invalidate". It may be related to what's in the cache or how full it is, because pausing the node shortly before the expected fail and then letting it proceed, also avoids the fail. Challenging to debug under those conditions.
[4:54 PM] kralverde 🤡 🇺🇸: Ill try some good ol fashioned print debugging
[5:37 PM] LSJI07: im mining currently on testnet. A good 0.7Mhs. Best to stop or continue to assist testing?
[5:37 PM] LSJI07: Running Testnet v4.7.0.0-b5010492c fdovs test3
[5:38 PM] LSJI07: and hi 🤣
[5:41 PM] kinkajou (SegWit Clique): I think Hans is asking that we run the current develop branch rather than test3
[5:42 PM] kinkajou (SegWit Clique): I've re-built from develop and syncing now
[5:47 PM] LSJI07: Swapped. Node running and mining the 4.8 binaries.
[5:51 PM] kinkajou (SegWit Clique): Awesome! I'm going to go ahead and close this channel. We can continue in development
Thanks for coming, everyone!

I did, hence I am posting these here.

Edit: I have been given an example. The misspelling of "freedom of speach" for example is so uncommon that it only gives 82 000 google results, while "freedom of speech" gives over 52 000 000 hits.
And in Ravencoin discord, since its inception in 2018, it has only been said twice and both times by the same person - Seal Clubber, while Photoshi Nakamoto used it also within a month on a discord server with only 500 people.

https://imgur.com/a/IUYYLM4
mirror:
https://ibb.co/SVLLFh2
https://ibb.co/gyZZYm2

Take your own advice, kid.

Maybe you should at least consult someone with an understanding of statistics before replying with such nonsense or perhaps you are well aware of the truth and just choose to hide it. "Seal Clubber" not only admitted it, but also matched with word and sentence usage perfectly, leaving no doubts.

https://imgur.com/a/IUYYLM4
mirror:
https://ibb.co/SVLLFh2
https://ibb.co/gyZZYm2

ur a shitcoin

Sure. LOL. There is nothing left but pump and dumps.

LMAO at you calling anything else a shitcoin. That is truly what RVN is right now. It is the true definition of a shitcoin.

I'm familiar with Bayesian statistics. Every actual social scientist I've worked with acknowledges their near-uselessness. Probabilistic conclusions are just that. Your attempt to draw definitive conclusions from probabilities and laughably small datasets highlights your vast misunderstanding of the subject and/or reveals your obvious attempt at trolling.

---

Dev Meeting Transcript (February 11, 2022)

[4:05 PM] BadGuyTy: Almost forgot again!
[4:05 PM] LSJI07 - BWS: I have made a brief list of items for today. Very brief unless someone has a longer agenda.
[4:05 PM] LSJI07 - BWS: 1. Update on the Ledger progress for rvn asset support. Is anything needed from the community to help progress.
2. Progress on p2sh and next wallet release.
[4:07 PM] kralverde  : Ledger is going slow but sure
[4:08 PM] BadGuyTy: My question on the next release is if its not coming soon can we maybe squeeze in mineable assets? Not sure how much more work that would be though
[4:08 PM] BadGuyTy: I would like to see those definitly before eth goes pos
[4:08 PM] kralverde  : https://github.com/kralverde/app-ravencoin here is the repo for ledger
[4:09 PM] kralverde  : Everything works but its unstable; crashes sometimes, finding out why
[4:09 PM] LSJI07 - BWS: Mineable assets would be a concensus change and bad practice imo to include more that one significant change in a release. P2SH is enough for the next release imo.
[4:09 PM] kralverde  : https://discord.com/channels/429127343165145089/819274815696797717/856684438254911529 and here is how to emulate
[4:09 PM] kralverde  : And if anyone wants to help feel free, written in c
[4:11 PM] BadGuyTy: sorry I got enough things I'm trying to do like make a pgp tag faucet and api for squawker
[4:12 PM] LSJI07 - BWS: I got given a ledger recently so can help test but not programming. I know my limits at the moment.
[4:14 PM] LSJI07 - BWS: Will make a community request though on as many channels as possible for devs to assist. Don't ask, don't get.
[4:15 PM] Tron: I'm back home.  I'll set some time aside next week to review PRs for inclusion.
[4:18 PM] LSJI07 - BWS: Thats awesome. Thank you! I saw quite a few small prs moving on github recently.
[4:18 PM] Hans_Schmidt: Most of the PRs have already been merged into develop. There are just a few more. And some cleanup.
[4:20 PM] BadGuyTy: I'm excited to add to the rvn dev movie! I need a cleaner way of including the btc code forks though those make the image jump all over the place.
[4:20 PM] Hans_Schmidt: Also, there is one more bug fix which I want to include in the next release. In December we had a report of a nasty bug in core which caused all the pool operators to lock up at the same time and require restarting. It was caused by a case in which miners were lucky enough to find two blocks less than one second apart. I'm in the process of writing up the PR bug fix for that.
[4:21 PM] BadGuyTy: my question is how did the miners know the question that fast to find the answer that fast
[4:22 PM] Someone_2: I remember reading about that.  Somehow 3 blocks were found inside of like 40 seconds of eachother and it did really bad things.
[4:22 PM] BadGuyTy: I remember it happening for sure
[4:23 PM] LSJI07 - BWS: pure chance imo. good to have a fix in the works. surprised testnet didnt have that bug though. found lots of blocks close together there.
[4:24 PM] BadGuyTy: yeah but on test net your not fighting with others for consensus
[4:25 PM] Hans_Schmidt: Testnet has had some other issues which look like they may be related, but it's hard to tell for sure since it's difficult to reproduce and the error messages are not very helpful.
[4:27 PM] BadGuyTy: good error messages are impossible
[4:27 PM] Hans_Schmidt: Plus the two blocks have to be REALLY close together.
[4:28 PM] BadGuyTy: sub second is highly unlikely. lets say 0.2 latency total thats 0.8 for a solution which is not long
[4:31 PM] Someone_2: despite 'close' being relative.  If I remember correctly, it was roughly that 3 blocks were found in under a minute(totally screwing up the average) and then nothing was found for like 10 minutes, perhaps evening out what had just happened, and it was wondered briefly if the chain had crashed.
[4:33 PM] LSJI07 - BWS: is anyone monitoring chain tips? and the longest fork?
[4:33 PM] LSJI07 - BWS: recently?
[4:34 PM] Tron: No, but near the halving the chain for NiceHash was out-of-sync.  Possible attempt at 51% attack.
[4:35 PM] LSJI07 - BWS: I personally haven't seen any significant splits longer that 10 blocks, normally hovering around 1 or 2 max.
[4:35 PM] BadGuyTy: I can't wait till the usage gets up there that that sort of thing is impossible.
[4:36 PM] LSJI07 - BWS: But that is very casual monitoring and not an in depth review.
[4:39 PM] LSJI07 - BWS: Wrapping a stability fix Hans mentioned and the P2SH code sounds fine imo as long as only one is consensus related.
[4:40 PM] BadGuyTy: So what are we thinking the new release date should be around?
[4:40 PM] LSJI07 - BWS: Preaching to the choir. I'll sit down.
[4:41 PM] BadGuyTy: assuming everything is approved and merged into dev what would we be looking at for a date?
[4:44 PM] Hans_Schmidt: They are both in consensus code but the bug fix is two lines of code.
[4:46 PM] Hans_Schmidt: Timing depends on multiple people to approve so it's not under any one person's control.
[4:50 PM] LSJI07 - BWS: Ok, I thought they could be. So double checking. Can we do 2 releases? 1 with the stability fix only (no BIP9) and one immediately after with P2SH (with BIP9)? That way people have the choice. I know its a PITA but its fairer to ensure P2SH consensus is clear. I dont believe a BIP9 is required for the stability consensus issue (tell me if I'm wrong here).
[4:53 PM] LSJI07 - BWS: The second release contains the stability fix plus P2SH (BIP-9) for clarity.
[4:54 PM] Hans_Schmidt: It can be one release with only the P2SH stuff wrapped up in the BIP9 miner approval.
[4:55 PM] LSJI07 - BWS: I like simple.
[4:58 PM] Hans_Schmidt: There are quite a few PRs that will be in the release which touch consensus code, but are not expected to have any effect on on-chain consensus. The <1sec block bug fix, for instance, is in the consensus section of code but shouldn't change what goes on the chain. The pools didn't put anything weird on the chain, they just looked up.
[4:59 PM] Hans_Schmidt: Most of those are code fixes ported from bitcoin.
[5:04 PM] LSJI07 - BWS: Thanks for the info and updates. Appreciate it. Thank you all for coming! :rvn_heart_2:
[5:04 PM] LSJI07 - BWS: I'm doing a runner.
[5:06 PM] Hans_Schmidt: The P2SH for assets feature needs BIP9 approval because it's a major feature change and also a massive amount of new code which affects consensus.
[5:42 PM] kinkajou (SegWit Clique): I'll go ahead and wrap this one up. Any further discussion can continue in development
Thanks for coming, everyone

[moderator's note: consecutive posts merged]

Hi, unfortunately I cannot satisfy your confirmation. You ought to read up on Bayesian statistics - it is quite simple.
You are harboring crypto scammers; perhaps you are in the crew. Each misspelling or 'special' word is only used by a small set of people inside the whole RVN community.
I.e. one word would only match a few people, as you can see for yourself by using the search function for the specific misspellings. When you choose a set that share two same misspellings, the group is already much smaller. Taking into account all the words, there is only one person that matches the description. No-one else comes even close.

https://en.wikipedia.org/wiki/Bayes'_theorem

The evidence is crystal clear.  Let us not forget, he also admitted to it.

https://imgur.com/a/IUYYLM4
mirror:
https://ibb.co/SVLLFh2
https://ibb.co/gyZZYm2

Using bayesian theorem and calculations I totally just did (trust me) I can 99.999% confirm you are mN, a disgruntled community member.

Sorry you got burned mining yet another shitcoin after being warned against. Shoulda just stuck with RVN instead of chasing scams.

---

Dev Meeting Transcript (February 4, 2022)

[4:00 PM] kinkajou (SegWit Clique): 👋
[4:01 PM] Someone_2: 👋
[4:01 PM] neil: I forgot about this
[4:04 PM] Someone_2: perhaps many others did too.  I had to set an alarm clock to be here.
[4:05 PM] kinkajou (SegWit Clique): That's what I do. Fridays are tough for meetings heh. Sometimes just takes a while for people to fill in too.
[4:05 PM] Someone_2: If not I may have just stumbled in at 3:25ish or some other time like that.
[4:09 PM] LSJI07 - BWS: Hi.
[4:11 PM] LSJI07 - BWS: Bless everyone's snoozing.
[4:11 PM] LSJI07 - BWS: Apologies. Most are snoozing. 😉
[4:18 PM] LSJI07 - BWS: question from @Raven Rebels Hi folks, does anyone know of a JavaScript-library that.
1) From 12 words can generate Ravencoin addresses ( BIP39 Mnemonic)
2) Can sign a certain message with a certain address/privkey?
[4:19 PM] LSJI07 - BWS: While its quiet.
[4:21 PM] LSJI07 - BWS: Because i dont know. I though there was a lib that worked early but nothing that has had a release afaik.
[4:22 PM] Raven Rebels: ravencore-lib?
[4:23 PM] LSJI07 - BWS: yes but it was before bip39 iirc.
[4:25 PM] Raven Rebels: Would be nice if we could have a Google Chrome extension so we could sign in to web sites using unique assets, (or addresses)
For that we need JavaScript
[4:26 PM] kinkajou (SegWit Clique): We were using pocketraven to generate a privkey from un+pw input
[4:26 PM] kinkajou (SegWit Clique): Never got signing down though
[4:27 PM] Raven Rebels: https://signin.ravenrebels.com/ this poc works, but you have to manually sign a message in Raven core QT
[4:27 PM] kinkajou (SegWit Clique): Yeah the goal was a browser extension to login to websites like you mentioned
[4:28 PM] kinkajou (SegWit Clique): @Scotty apparently had keyvault working on RVN at one point but no one was using/testing it
[4:29 PM] Raven Rebels: Googled and found it, will check it out
[4:31 PM] LSJI07 - BWS: https://discord.com/channels/429127343165145089/429133749867905024/807016002718138458
[4:31 PM] kinkajou (SegWit Clique): Oops sorry I mentioned it in a few meetings but here is link for reference: https://demos.keyvault.app/
[4:31 PM] Raven Rebels: Thank you.
[4:34 PM] LSJI07 - BWS: https://github.com/RitoProject/bip39 this can be used to get an address from a seed.
[4:34 PM] LSJI07 - BWS: setup for rito but the same concept works for rvn.
[4:35 PM] Raven Rebels: Thanks will check that out
[4:35 PM] LSJI07 - BWS: https://github.com/iancoleman/bip39 this is the original.
[4:37 PM] kinkajou (SegWit Clique): @kralverde 🤡 🇺🇸 sent me this library when I mentioned our signing issue but I haven't looked at it yet since we scrapped the project: https://github.com/starkbank/ecdsa-node
[4:38 PM] Raven Rebels: Will check that one out, as well.
This works, apparently, but it is not clear HOW it works 😉
https://ravencoin.org/bip44/
[4:40 PM] LSJI07 - BWS: @Raven Rebels the keys are deterministic so the same seed can be used for multiple blockchains.
[4:42 PM] Raven Rebels: true
[4:42 PM] LSJI07 - BWS: just a different paths.
[4:42 PM] Raven Rebels: m/44'/175'/0'/0 for Raven I assume
[4:43 PM] Raven Rebels:
Image
[4:43 PM] LSJI07 - BWS: yes. and bip32 is m/44'/0'/0'/0
[4:44 PM] Raven Rebels: bip39 package is lovely. So getting the word list easy.
[4:45 PM] Raven Rebels: I thought m/44'/0'/0'/0 was for BTC and m/44'/175'/0'/0  was for RVN
[4:47 PM] LSJI07 - BWS: you are right.
[4:47 PM] LSJI07 - BWS: reading fast sorry!
[4:48 PM] Raven Rebels: Any news on the new mobile wallet?
[4:50 PM] LSJI07 - BWS: @WhaleStreet
[4:52 PM] LSJI07 - BWS: This is the last update I saw.
Image
[4:53 PM] Raven Rebels: That was almost 6 weeks ago 😉
[4:54 PM] LSJI07 - BWS: Quietly waiting. Or at least trying to...
[4:54 PM] Raven Rebels: We really need solid smartphone wallets. That combined with "sign in to web apps using Ravencoin NFTs"
[4:55 PM] LSJI07 - BWS: I need that for a few discords. Simply to keep bots out.
[4:57 PM] kinkajou (SegWit Clique): People keep telling me "it's not that hard" for like 2+ years now but we still have none.
No one likes JS imo
[4:59 PM] kinkajou (SegWit Clique): I think Mango said he might consider making one eventually a few dev meetings back
[4:59 PM] Raven Rebels: Sorry, what do they say is not hard?
[4:59 PM] kinkajou (SegWit Clique): Making a browser extension to sign into web applications with RVN assets
[5:00 PM] Raven Rebels: Shouldnt be hard.
Well we have to store your secrets (phrase) in a very safe way. Well, copy how meta-mask is doing.
[5:01 PM] kinkajou (SegWit Clique): Can't you just keep it encrypted in sessionmem?
[5:01 PM] kinkajou (SegWit Clique): Tried forking metamask first and it was just a complete waste of time. Entirely different from what you'd want for BTC based chains IMO
[5:01 PM] kinkajou (SegWit Clique): easier to start from scratch
[5:03 PM] Raven Rebels: yes we should start from scratch
[5:04 PM] Raven Rebels: The flow, to sign in by signing a message is not complicated
[5:04 PM] Raven Rebels: This demo should work https://signin.ravenrebels.com/
[5:04 PM] Raven Rebels: But you have to manually sign a message in Raven core QT (sorry for saying this twice)
[5:05 PM] LSJI07 - BWS: All the site does is verify. Shouldnt have to have anything with private keys imo. Only the public key for the user and unsigned message. Response is the signed message. Am i missing something?
[5:05 PM] Raven Rebels: This demo works like this
[5:05 PM] Raven Rebels: USER, enters the name of the NFT the user wants to sign in as
[5:06 PM] Raven Rebels: SERVER: checks the network, which address the NFT belongs to and generates a message/challenge
[5:06 PM] Raven Rebels: USER, takes the message/challenge and signs it
[5:06 PM] Raven Rebels: User sends the signed message to server
[5:06 PM] Raven Rebels: SERVER: validates that the message has been signed with the correct address (that holds the NFT)
[5:06 PM] LSJI07 - BWS: So we just need a way to verify the signed message without a wallet.
[5:07 PM] kinkajou (SegWit Clique): Yeah that part just really kills the UX and hinders adoption though IMO
[5:07 PM] kinkajou (SegWit Clique): better to have it all in the browser
[5:07 PM] Raven Rebels: If we have a browserextension, where I have endered my phrase or my private key.
[5:07 PM] Raven Rebels: Then the browser extension can sign the message, and the ux-flow is silky smooth for the end user
[5:08 PM] Raven Rebels: Just a prompt "Do you want to sign in to...." and you click YEZZ!
[5:09 PM] LSJI07 - BWS: So extension is a hot wallet used to simply verify the login signed message. 👍
[5:09 PM] Raven Rebels: almost, its a hot wallet used to sign the message.
[5:09 PM] Raven Rebels: user never verify, only sign, server only verify, never sign
[5:11 PM] Raven Rebels: bitcore-message seems promising, will check it out right away
[5:11 PM] LSJI07 - BWS: https://github.com/raven-community/ravencoinjs-message
[5:12 PM] LSJI07 - BWS: @Raven Rebels like this.
[5:16 PM] Raven Rebels:
Image
[5:17 PM] Raven Rebels: The first example throws an error unfortunately
[5:19 PM] Raven Rebels: Seems a bit outdated.. too bad, we need this 😉
[5:19 PM] LSJI07 - BWS: https://github.com/kralverde/ravencoinjs-message has 2 new commits.
[5:21 PM] LSJI07 - BWS: @kralverde 🤡 🇺🇸 don't know if you had any joy with this?
[5:22 PM] kralverde 🤡 🇺🇸: One sec
[5:24 PM] kralverde 🤡 🇺🇸: Ive found better luck with bitcoin-js
[5:25 PM] kralverde 🤡 🇺🇸: Example with an asset minting discord bot (wip) https://github.com/kralverde/RavenDiscordBot/blob/master/main.js
[5:26 PM] kralverde 🤡 🇺🇸: https://github.com/kralverde/bitcoinjs-lib
[5:26 PM] Raven Rebels: Will bookmark that one
[5:26 PM] kralverde 🤡 🇺🇸: Thats the one i use to remove the buffer check for assets ^
[5:26 PM] kralverde 🤡 🇺🇸: But yeah bitcoin-js should be fine for generic stuff
[5:27 PM] LSJI07 - BWS: Awesome I think we can close the meeting now I need a liqueur coffee.
[5:27 PM] LSJI07 - BWS: 😋
[5:28 PM] LSJI07 - BWS: Hope that helps.
[5:28 PM] Raven Rebels: haha, thanks for all the help!♥
[5:29 PM] LSJI07 - BWS: @kralverde 🤡 🇺🇸 thank you for sharing that!
[5:45 PM] RAVENCOIN.TIMELINE.OVH: Hi guys, I would like to monitor specific RVN ASSETS  activity through www.RVN-Dashboard.com
For this, I need to find a way to get data daily:

I need to track activity of specific assets in terms of:
- number of transactions
- transferred volume (asset, not RVN)
- paid fees
- type of tx (issue, reissue, transfer)

Can this be done through a RVN node rpc calls ?
[5:47 PM] kralverde 🤡 🇺🇸: With pure node calls? No
[5:47 PM] RAVENCOIN.TIMELINE.OVH: how would it be possible ?
[5:48 PM] kralverde 🤡 🇺🇸: Periodically asking the node for the current height, when you see a new block, grab its data and parse it for what you need
[5:49 PM] RAVENCOIN.TIMELINE.OVH: So we need to scan each block, each minute … ?
[5:50 PM] kralverde 🤡 🇺🇸: Yeah
[5:50 PM] kralverde 🤡 🇺🇸: But id ask for the block height every like 2 seconds
[5:51 PM] LSJI07 - BWS: zmq?
[5:51 PM] kralverde 🤡 🇺🇸: You could do that
[5:51 PM] kralverde 🤡 🇺🇸: But its a little difficult for the whole getting the history thing
[5:52 PM] RAVENCOIN.TIMELINE.OVH: Ideally , we would need an api whereby se enter the asset name, the date, and a summary get returned
[5:53 PM] kralverde 🤡 🇺🇸: Nah
[5:53 PM] kralverde 🤡 🇺🇸: I mean
[5:53 PM] kralverde 🤡 🇺🇸: All the data is there
[5:54 PM] kralverde 🤡 🇺🇸: But building this niche case into core is not necessary in my eyes
[5:55 PM] RAVENCOIN.TIMELINE.OVH: The idea behind this project is to monitor ASSET activity, to follow a project. Ie: Stable Coin on RVN Blockchain … we could monitor to per day, transfers … then put the result on a chart and see how successful / how much it is used.
[5:55 PM] kralverde 🤡 🇺🇸: I get what youre saying
[5:55 PM] kralverde 🤡 🇺🇸: Its going to be a fairly sizeable database tho
[5:56 PM] kralverde 🤡 🇺🇸: Do you wanna only store current data or by height?
[5:56 PM] RAVENCOIN.TIMELINE.OVH: I have a vps and would not mind hosting the db
[5:56 PM] LSJI07 - BWS: the database is already there if the user is storing assetindex and addressindex anyway.
[5:57 PM] RAVENCOIN.TIMELINE.OVH: Basically, I am not technical , not programmer … I have ideas … I would like to get all useful data per day that can be useful to monitor any asset names.
[5:58 PM] kralverde 🤡 🇺🇸: Yeah its simple enough
[5:58 PM] RAVENCOIN.TIMELINE.OVH: Then I can add them on RVN- dashboard.com…. Available for anyone
[5:58 PM] kralverde 🤡 🇺🇸: I could probably write one up for you over the weekend
[5:58 PM] kralverde 🤡 🇺🇸: Just dm what you want
[5:59 PM] RAVENCOIN.TIMELINE.OVH: I will do, thanks!
[6:15 PM] RAVENCOIN.TIMELINE.OVH: Done
[7:09 PM] WhaleStreet: Getting closer, we all caught covid for two weeks. We are making good progress and everyone will be pleased with our hard work!
[7:15 PM] LSJI07 - BWS: @WhaleStreet take care! 🙏
[7:19 PM] kinkajou (SegWit Clique): I will go ahead and close the channel now. Further discussion can continue in development
Thanks for coming, everyone!

Ravencoin mod Seal Clubber#4158 is a crypto scammer.
 
User ID: 182861110796353536
Username: Seal Clubber#4158
Created: Thu, 19 May 2016 14:24:46 UTC

His most recent scam was Photonic Bitcoin with the nickname Photoshi Nakamoto, where he forked Optical Bitcoin with his friends and promised heavy development, youtube advertisement and such and delivered nothing. Shortly after joining Exbitron-exchange the network was controlled 95% by FPGA party and the coins were autoexchanged - dumped - into BTC.

 User ID: 846157505846444033
 Username: Photoshi Nakamoto#5052
 Created: Sun, 23 May 2021 22:47:50 UTC

Other people involved in dev team:

 User ID: 828817220137517107
 Username: Kev9#3438
 Created: Tue, 06 Apr 2021 02:23:43 UTC

 User ID: 108660815107768320
 Username: Pharin#5976
 Created: Tue, 27 Oct 2015 20:19:17 UTC

 User ID: 889539725122220032
 Username: Fojo#8677
 Created: Mon, 20 Sep 2021 15:53:17 UTC

 User ID: 159334643777142784
 Username: OhGodAGirl#8787
 Created: Tue, 15 Mar 2016 16:18:59 UTC

edited: new picture links.

https://imgur.com/a/IUYYLM4
mirror:
https://ibb.co/SVLLFh2
https://ibb.co/gyZZYm2

Using bayesian theroem it can be confirmed he has used this discord account 99.999...%, in pm's he is just confirming it.