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

What do you mean will be back on the exchanges for trading? from what I see RavenCoin (RVN) already listed on several popular exchanges including Binance
It's just that the price is currently falling almost to its lowest point but it's normal because it's not just Ravencoin, other coins are experiencing it too
If you are part of the community then this is the right time to buy right?

Dev Meeting Transcripts (May, 2022)

[4:00 PM] kinkajou (SegWit Clique): Channel open
[4:08 PM] CryptoLifeCrisis: Any devs doing dev stuff? 😛
[4:11 PM] CosmicDruid 🅁🅅🄽: Well, I am developing a Ravencoin Framework, over at: https://ravencoinhelper.com/
[4:11 PM] CosmicDruid 🅁🅅🄽: its up, and running, and people are using it. I have put it into Beta for others to get involved...
[4:16 PM] JustaResearcher: Would really love to get segwit integrated into RVN. Would be nice to get an idea of how much that would cost.
[4:19 PM] kinkajou (SegWit Clique): Same. If any of our @Core Developer have a rough estimation it would probably be easier to start crowdfunding. Perhaps we could get a funding proposal page on the foundation site like we did for the stablecoins. An issue was created a while back: https://github.com/RavenProject/Ravencoin/issues/979
[4:25 PM] Nonprophete: Per the previous post from Hans it appears the sync bug is now finally fixed so I'm curious when is P2SH going live onto the chain?
[4:26 PM] Nonprophete: any ETA?
[4:26 PM] kinkajou (SegWit Clique): @Tron was working on those 6 failing tests not sure if he is around to give us a progress update this week?
[4:26 PM] kinkajou (SegWit Clique): I think that is the only thing holding up release.
[4:28 PM] α | crypticwizardry.com: Working on those pool scripts lol
[4:28 PM] α | crypticwizardry.com: Finals ended yesterday, so free to begin that and plunging into mineable assets
[4:29 PM] CosmicDruid 🅁🅅🄽: WooHoo! more burning of the midnight oil i bet!
[4:53 PM] Seal Clubber: Segwit would be cool with p2pool, great for having more nodes running
[4:56 PM] CosmicDruid 🅁🅅🄽: I'd like to know if anyone has a library for creating a new address, without? booting up ravend?
[4:57 PM] CosmicDruid 🅁🅅🄽: I'll be tying up the ipfs PeerID with a RVN address right when a user starts https://ravencoinhelper.com/ up for the first time.. so I can tie them both in with the Token I will be giving them: 1 Token every 24hr. PoW...
[5:35 PM] CosmicDruid 🅁🅅🄽: What i am currently doing is this:
[5:35 PM] CosmicDruid 🅁🅅🄽: * creating the basic "files" that ravend starts for the first time, BUT, delete the wallet.dat  then -> tar them up.
[5:36 PM] CosmicDruid 🅁🅅🄽: * on first run of ravencoinhelper.com I untar the basic files.
[5:36 PM] CosmicDruid 🅁🅅🄽: * systemctl --now enable ravend (which also re-creates the wallet.cat) so that it is UNIQUE.
[5:37 PM] CosmicDruid 🅁🅅🄽: then do a raven-cli getnewaddress to a file.
[5:37 PM] CosmicDruid 🅁🅅🄽: this and the IPFS PeerID gets sent via scp (private/public key) to the server, including an email address IF the user wants to send it for notifications...
[5:37 PM] CosmicDruid 🅁🅅🄽: server side parses both bits of data...
[5:38 PM] Seal Clubber: You could lookup how the paper wallets generate them
[5:38 PM] CosmicDruid 🅁🅅🄽: I "feel" there is a better way to generate a RVN address than what i have right now. anyone know of a way?
[5:38 PM] CosmicDruid 🅁🅅🄽: oh? got a link?
[6:03 PM] kinkajou (SegWit Clique): https://github.com/RavenCommunity/pocketraven
[6:20 PM] CosmicDruid 🅁🅅🄽: ok cool. i'll check out that link
[6:20 PM] CosmicDruid 🅁🅅🄽: thank you!
[7:30 PM] LSJI07: I aint gonna lie. Sometimes just ask the user for the rvn address they want to use. Keep it simple.
[8:42 PM] BadGuyTy: is there a reason dev meetings is still open. been sick all afternoon just getting to my chair now.
[8:46 PM] BadGuyTy: I just use the address they send their message from 🙂
[8:54 PM] kinkajou (SegWit Clique): Yes, we've been waiting for you.
[8:55 PM] kinkajou (SegWit Clique): Or hoping a core dev might have something to add in regards to SegWit/those failing tests but I guess they can post when channel is locked so I'll close it now.
----------
[1:12 PM] Tron: I will not make it for today's dev mtg - on a flight.
[4:00 PM] kinkajou (SegWit Clique): Channel open
[4:02 PM] Blockchain John: @BadGuyTy Dev Meeting started.
[4:02 PM] BadGuyTy: thanks
[4:05 PM] Blockchain John: What's on the agenda? @kinkajou (SegWit Clique)
[4:06 PM] kinkajou (SegWit Clique): Only item I had was hoping for an update on those failing tests but Tron is not present and he was the one working on that
[4:06 PM] kinkajou (SegWit Clique): Does anyone have anything else theyd like to discuss?
[4:06 PM] LSJI07: QC
[4:06 PM] BadGuyTy: I would just like to complain about the low understanding of blockchain and wasted my time this morning with no real discussion on web3
[4:06 PM] LSJI07: 🤣
[4:07 PM] CosmicDruid 🅁🅅🄽: i'm watching 😄
[4:08 PM] Blockchain John: I'm hearing alot of talk about pRVN in Twitter. Have you guys been keeping up in the development?
[4:10 PM] kinkajou (SegWit Clique): @CryptoLifeCrisis has taken it upon himself to get that bridge back up. I'm interested in helping as well. We both agree that the ability to bridge RVN NFT's to a metamask-compatible smart-chain would be huge for Ravencoin adoption.
[4:13 PM] BadGuyTy: I am trying to actually build a ravencoin metamask esk extension
[4:14 PM] BadGuyTy: it looks like moontree won't initially have that so I am implementing it immediately after I implement a rip11 decryption plugin.
[4:16 PM] kinkajou (SegWit Clique): That would be huge for Ravencoin as well. Anything to increase usability. Also opens up a lot of web3 potential for token-based authentication/authorization. Isn't squawker currently using some version of this as well?
[4:16 PM] BadGuyTy: I think that that is what is needed for squawker to take off
[4:17 PM] BadGuyTy: yes squawker has wallet signing to login
[4:18 PM] BadGuyTy: the squawker api can actually handle that back end for you
[4:19 PM] BadGuyTy: I know synth has expressed interest in using it and think has started some projects with it
[4:20 PM] kinkajou (SegWit Clique): If I can use it from my browser I will definitely start squawking
[4:21 PM] BadGuyTy: well right now it is all browser based but needs the wallet signatures
[4:21 PM] BadGuyTy: hoping to be able to tie into moontree for the signing
[4:21 PM] kinkajou (SegWit Clique): yes manual signing is very tedious
[4:21 PM] kinkajou (SegWit Clique): and confusing for novice users
[4:22 PM] BadGuyTy: I think my guide isn't horrible
[4:22 PM] kinkajou (SegWit Clique): Absolutely not! I'm js most people wont take the time to look for a guide
[4:22 PM] kinkajou (SegWit Clique): theyll look at the app and if they cant figure it out theyll close the browser
[4:22 PM] kinkajou (SegWit Clique): at least thats my impression
[4:22 PM] Blockchain John: Any instructional videos available to learn how to use squeaker?
[4:23 PM] BadGuyTy: my guide is on the side of the site.
[4:23 PM] BadGuyTy: just txt and photos
[4:24 PM] BadGuyTy: https://squawker.app/
[4:26 PM] BadGuyTy: I do need to do some instructional videos but I think getting an in browser wallet will eliminate that barrier
[4:28 PM] BadGuyTy: just not enough time to carry it myself
[4:28 PM] kinkajou (SegWit Clique): maybe you could post a bounty here in the discord!
[4:29 PM] kinkajou (SegWit Clique): general-bounties coding-and-testing-bounties volunteers-needed
[4:29 PM] BadGuyTy: bounty? I aint got that kinda money. If I did I would quit my job and go all ham on it
[4:30 PM] kinkajou (SegWit Clique): Bounty rewards can also be NFTs, or you could post a volunteer bounty
[4:32 PM] BadGuyTy: I got the block_chaingang nfts but they wouldn't even sell for 100 rvn
[4:33 PM] kinkajou (SegWit Clique): I've done a lot more for a lot less 😅 someone might pick it up. Just know that you have a resource available to request community assistance if you choose 🙂
[4:35 PM] BadGuyTy: I'm hoping once I get the rip11 decode done I get picked up as a dev for a blockchain project
[4:42 PM] Blockchain John: I recently downloaded the entire Blockchain QT fully loaded. 50GB. Now that I have it, I want to tinker with some additional commands.
Any suggestions?
[4:46 PM] BadGuyTy: I gotta go get the kids but @Blockchain John I would play with finding a decoding txs personally
[4:52 PM] Blockchain John: What I really want to do is get some help creating a IPFS NODE to store all the NFT/Assets images, video, sounds, text. It's sad to see that many assets/coins) NFTs are missing images.
[4:53 PM] M4R1M0: @CosmicDruid 🅁🅅🄽 is your guy for that! Check out https://ravencoinhelper.com/ravencoinhelper-for-windows-10/
[4:55 PM] Blockchain John: It's not currently functional.
[4:57 PM] kinkajou (SegWit Clique): :soontm:
[4:59 PM] Blockchain John: We should definitely have much more RVN IPFS NODES.
[4:59 PM] Blockchain John: As the network grows we need to support IPFS PEERS
[5:02 PM] LSJI07: You could use this script to add new hashes to your ipfs node from your ravencoin node.
[5:02 PM] LSJI07: https://github.com/RavenProject/Ravencoin/blob/master/assets/tools/txfacts.py
[5:03 PM] LSJI07: Cosmics helper virtual machine and RavenlandsOS are easier imo, but the option is there.
[5:16 PM] kinkajou (SegWit Clique): @Blockchain John I'm using @CosmicDruid 🅁🅅🄽 's RavencoinHelperOS on Windows now. Which part isn't working?
[5:28 PM] LSJI07: Im using the helper on windows as well at the moment. Working for me.
[5:58 PM] kinkajou (SegWit Clique): I'll go ahead and close the channel. Can continue discussion in development
Thanks for coming, everyone
----------
[4:00 PM] kinkajou (SegWit Clique): Channel open
[4:15 PM] BadGuyTy: any updates on the new version?
[4:15 PM] kinkajou (SegWit Clique): @Tron have you made any progress?
[4:16 PM] kinkajou (SegWit Clique): Also appears Bittrex is having issues with their node. It has been down for a few weeks now.
[4:16 PM] BadGuyTy: really how does your node go down for a few weeks?
[4:16 PM] Mango Farm: See Haxmat’s note in the development channel
[4:16 PM] BadGuyTy: especially with an active discord
[4:17 PM] Tron: I've emailed Bittrex, but have not heard back.  Many of the original contacts I had with exchanges were lost when I lost access to my Medici Venture e-mail.
[4:18 PM] Mango Farm: @haxmat can you let tron know the contact that reached out to you?
[4:18 PM] Tron: So, I'm reliant on the public info.  I e-mailed [email protected] on May 10th and still no response.  I offered to help them, or at least to understand the problem.
[4:19 PM] Tron: @haxmat Please DM me or e-mail me [email protected] with the right contact info.
[4:19 PM] Mango Farm: Tron - https://discord.com/channels/429127343165145089/429133749867905024/977259619770568704
[4:21 PM] BadGuyTy: hmm so new release version?
[4:24 PM] Tron: We need to think about P2SH in the context of audit-ability of assets.
[4:24 PM] kralverde 🤡 🇺🇸: I am in contact with bittrex, if you want me to patch you thru
[4:24 PM] Tron: As it stands now, the assets issued will always match assets in addresses.
[4:24 PM] Tron: Yes, please.  Preferably to [email protected].
[4:25 PM] BadGuyTy: but you are thinking that with p2sh that we might have a situation where they build or want a multisig address?
[4:25 PM] Tron: With P2SH, the script is hidden, and only the hash of the script is on-chain until the script and script solution are published.
[4:26 PM] Tron: As it is now, the system can make some guarantees that are useful.
[4:27 PM] Tron: 1000 shares issued, and 1000 shares are in X number of addresses.
[4:27 PM] Tron: There's an audit script that will check this integrity.
[4:27 PM] Tron: --------------------
[4:28 PM] Tron: Does anyone know of anyone that is waiting for P2SH to do their project?
[4:28 PM] BadGuyTy: but with the p2sh you can't guarentee it until after the solution is know which means we might need some safeguards around solutions getting pulled from the mempool that while valid are invalid from restricted asset protections?
[4:29 PM] BadGuyTy: I was going to go that route (p2sh) but went with send by proxy where you just have to have the info signed from the wallet
[4:29 PM] kinkajou (SegWit Clique): There has been a lot of interest in the ability to utilize cross-chain atomic swaps with Ravencoin Assets
[4:31 PM] BadGuyTy: That is the main use case that I have seen too
[4:31 PM] kinkajou (SegWit Clique): Could the issue be prevented if regulatory compliant projects simply don't issue qualifier tags to multisig addresses?
[4:32 PM] BadGuyTy: that is a very good restriction
[4:32 PM] BadGuyTy: and if its for regulatory compliance its a completely reasonable request to keep everything in the open
[4:36 PM] Mango Farm: Not us but there is some unreleased code unrelated to P2SH including bug fixes that we do use that has been waiting on the next release.  Asset memo raw transactions won’t build in the current production release.  We have a special api that uses Fdov’s fix from a couple of months back but things like that seem to be waiting on the big P2SH roll.
[4:37 PM] BadGuyTy: oh hey that was the bug I found
[4:37 PM] Mango Farm: Nice
[4:37 PM] Mango Farm: Well thank you it was the thing that kept us from putting memos on assets
[4:38 PM] BadGuyTy: yeah the code was completely commented out. I was trying to learn raw txs for squawker and it just wasn't working
[4:38 PM] CosmicDruid 🅁🅅🄽: thanks @kinkajou (SegWit Clique) !
[4:39 PM] Tron: I guess what I'm trying to convey is that we have a trade-off.  We currently have auditable assets, which seems very valuable.  We may have to sacrifice that for P2SH, and it may or may not be worth it if there aren't projects needing P2SH.  The other fixes can be done independent of P2SH.
[4:40 PM] BadGuyTy: Well what would be the down side of not allowing p2sh for restricted assets
[4:41 PM] Mango Farm: Tron - I wonder if it would be possible to solve that trade off by allowing issuers, at the time of original issuance, to restrict assets to only pubkey hashes - sort of like restricted assets but more generalized to all addresses (but only addresses).  Anyway that sprung to mind but it’s a whole thing.
[4:41 PM] Tron: Second question.  Since you @Mango Farm are using the fixes on the current chain, those fixes are not consensus impacting and could be used now.
[4:42 PM] kinkajou (SegWit Clique): Can this not already be achieved with restricted assets and qualifiers?
[4:42 PM] Mango Farm: Exactly - we’ve got them running on a separate API just for memo txs.  All good it’s just not the easiest for others who might want to do the same with asset memos.  We are good for now Tron.
[4:43 PM] BadGuyTy: the issue is that you don't know exactly where everything truely is that is behind a p2sh contract
[4:43 PM] Mango Farm: Probably but thinking more like a “one click” restriction that restricts to all possible addresses (p2pkh) without the need for a tag.
[4:43 PM] Tron: P2SH doesn't just impact Restricted Assets.  The audit-ability of all assets would be impacted.  With just pay-to-pub-key we can make sure that inputs = outputs for assets.
[4:43 PM] kinkajou (SegWit Clique): Right but it's easy enough to tell if an address is P2PKH, no?
[4:43 PM] BadGuyTy: completely blocks squawker from raw tx
[4:43 PM] kinkajou (SegWit Clique): Agreed this would be better.
[4:44 PM] BadGuyTy: the thing is that a p2sh could actually be bound for a p2pkh address
[4:44 PM] kinkajou (SegWit Clique): I'm just not so worried about the auditability of regular assets since projects aiming to be regulatory compliant will likely have to use restricted assets/tags anyway.
[4:45 PM] Mango Farm: Tron your point is a pretty important one, especially since the genesis of Ravencoin had something to do with the Dole Foods auditability issue.  It’s sort of the core of the whole thing.
[4:45 PM] Mango Farm: Point ☝️
[4:47 PM] BadGuyTy: yeah if you have a regular asset you should not be trying to keep it auditable. Restricted assets are easy enough to build and manage.
[4:49 PM] Tron: I know this is a limited sample size, but does everyone here think it is worth giving up asset audit-ability (gurantee of all issued = sum of all in addresses) in exchange for P2SH?
[4:50 PM] BadGuyTy: well how would you differ that number? the assets can't just disapear
[4:51 PM] BadGuyTy: i guess they would be sitting at some unknown utxo
[4:51 PM] CosmicDruid 🅁🅅🄽: I'd like to make a request please? i'm working with a few others in having clustered Ravencoin IPFS servers. at least 3 of them. and I was wondering if anyone has a list of "dead" ipfs hashes of the ravencoin blockchain?
[4:52 PM] kinkajou (SegWit Clique): I'd like to explore something like @Mango Farm proposed first. A "check box" to allow for P2SH would be ideal.
I do think having the ability to swap Ravencoin Assets for Bitcoin without a trusted third party is perhaps equally important as auditability.
[4:52 PM] Mango Farm: Tron - You would still be able to verify the total supply issued, right?  And the script a given quantity is locked to.  You wouldn’t be able to tie each asset to an address, but you would be able to tie all assets to an on-chain script.
[4:52 PM] BadGuyTy: would the p2sh break things like dividends assuming they were trying to send them to non resricted assets
[4:53 PM] Mango Farm: Yes I have this
[4:53 PM] BadGuyTy: yeah not all addresses but all utxos
[4:54 PM] CosmicDruid 🅁🅅🄽: i know you do. but your so busy! didn't want to bug you anymore
[4:54 PM] Mango Farm: It’s no bother.
[4:54 PM] CosmicDruid 🅁🅅🄽: oh sweet, thank you!
[4:54 PM] Tron: I don't know if this has been tested.
[4:54 PM] CosmicDruid 🅁🅅🄽: and peering of course... as agreed! I honestly don't like the clustering mode..
[4:55 PM] CosmicDruid 🅁🅅🄽: ravencoinhelper.com uses the peering, BUT, also limits the size of the ravencoin asset, and the diskspace the ipfs server can have.
[4:58 PM] kinkajou (SegWit Clique): I think a lot of people have been waiting on P2SH for over a year now and it has obvious benefits. I don't like the idea of simply tossing it out because it might cause problems in the future - so long as these problems can be avoided by utilizing Ravencoin's other tools. Which it seems like they can.
[5:00 PM] Morgan:
[5:00 PM] Morgan: This goes all over my head here but i just wanted to hop in and say Thank you to everyone working on development!
[5:02 PM] Seal Clubber: I would like to thank kral and hans for allowing us to mine testnet witout relying on closed source options
https://github.com/kralverde/ravencoin-stratum-proxy
https://github.com/hans-schmidt/kawpow_personal_stratum_server
[5:07 PM] BadGuyTy: ok so we should make a test for p2sh dividends in testnet.

 could you use the same script as the current utxo has? If it is going to evaluate the same that should be fine right?
[5:07 PM] BadGuyTy: have the other failure cases been resolved?
[5:09 PM] Tron: At least we should understand how a P2SH transaction impacts the audit (sum of assets), and how it reports for dividend purposes.
[5:10 PM] kinkajou (SegWit Clique): @Core Tester if any of you are available to help test this week it would be appreciated :rvn_heart_2:
[5:11 PM] CosmicDruid 🅁🅅🄽: i'll say it for myself. i'm saying.. NA. only because #1 out of a bit of ignorance, and #2 "not being able to see" before hand. reminds me of contracts. and all the scams that come with it, and the black eyes that the coin gets from it... just.. putting it out there as its not being said.
[5:11 PM] CosmicDruid 🅁🅅🄽: I reserve the right to be partially ignorant 😛
[5:12 PM] Mango Farm: @CosmicDruid 🅁🅅🄽 https://ravencoinipfs-gateway.com/ipfs/QmVFT2WGX9q2j5Xd6Ly4biBhE3p1GZWd7KbDaHXjQYrzSM 👈  run a recursive pin on that and sort out anything that pins it's been a minute since I went back over the whole thing to see if anything has since been found.  There may be a handful.
[5:13 PM] kinkajou (SegWit Clique): I think you owe it to yourself to dig into the issue a bit more since it impacts a consensus level change that we've already paid for and spent a year testing
[5:13 PM] CosmicDruid 🅁🅅🄽: @Mango Farm thank you i got it! I really appreciate it, and YOU..
[5:13 PM] Mango Farm: 👍  any time
[5:14 PM] CosmicDruid 🅁🅅🄽: @kinkajou (SegWit Clique)  ok. i will.
[5:14 PM] CosmicDruid 🅁🅅🄽: i'm slowly getting there 😛
[5:17 PM] Mango Farm: This is outstanding.  I didn't know about these.  Thank you both!
[5:17 PM] BadGuyTy: I think if we know the full effects that it is going to have and make restricted asset holders aware of those risks and restrictions it will be fine.
[5:18 PM] kinkajou (SegWit Clique): Perhaps if RavenCore issued a warning before assigning a qualifier asset to a non-P2PKH address?
[5:18 PM] BadGuyTy: I would offer to test it more myself but I am having a hard enough time getting out what I want to get out let alone that it looks like I will be writing a js provider class for ravencoin also
[5:19 PM] BadGuyTy: how many of those that are using p2sh assets are going to be submitting them through ravencore and not just submitting them to the mempool as raw txs
[5:20 PM] BadGuyTy: @Mango Farm  if you tell me you have a js provider class like metamask I will love you forever
[5:23 PM] BadGuyTy: What I really want is to get paid to write it if it isn't there already.
[5:24 PM] CosmicDruid 🅁🅅🄽: hey, when I make ravencoinhelperOS PoW with both client side AND serverside info put into github, could I get something from the foundation?
[5:25 PM] BadGuyTy: I'm not holding out hope for squawker on getting foundation money
[5:26 PM] Mango Farm: Sorry, Ty - no it's all in-house currently.  It's something we have wanted to do.
[5:27 PM] Mango Farm: So many days, so little time!
[5:27 PM] BadGuyTy: I don't mind in house as long as im in the house in question.
[5:28 PM] kinkajou (SegWit Clique): I think the foundation supports RavenCore development but I know they host bounties for other development like the stablecoin proposals
[5:28 PM] kinkajou (SegWit Clique): Idk we have two members in here don't we? 😆
[5:30 PM] BadGuyTy: can we get a bounty for a js provider? I would chip in a few grand raven towards that one
[5:31 PM] Mango Farm: Don't know if Tron is still in.  Here you go ... https://ravencoin.foundation/proposals
[5:32 PM] Mango Farm: email him @ the address linked
[5:34 PM] BadGuyTy: oh dang! minable assets is 10K
[5:36 PM] Tron: The foundation can help with proposals/grants.  It exists to support the ecosystem.  I does not have a regular source of funds and was not funded via ICO.  If there is a proposal and a will for participants to fund it, the foundation can help.  There are two stablecoin proposals now, and a bounty.
[5:36 PM] kinkajou (SegWit Clique): Are you still president of the foundation?
[5:37 PM] BadGuyTy: last week when we met he introduced that way.
[5:38 PM] BadGuyTy: wow it has been a long week.
[5:38 PM] kinkajou (SegWit Clique): I was just wondering because of Mango's comment just now https://discord.com/channels/429127343165145089/482289959261175838/977322711644782632
[5:38 PM] Mango Farm: Sorry guys I meant that I didn't know if Tron was still in the channel
[5:38 PM] kinkajou (SegWit Clique): OHHHH lol phew
[5:38 PM] kinkajou (SegWit Clique): had a bit of an internal panic there
[5:38 PM] BadGuyTy: thats the way i read it
[5:38 PM] Mango Farm: I didn't want to step on him since yes he is the president
[5:38 PM] kinkajou (SegWit Clique): My mistake.
[5:39 PM] Mango Farm: Sorry for the confusion I've got a couple screens up : )
[5:40 PM] Mango Farm: I just didn't want to jump in and respond if he was about to but then figured after a minute I'd drop his email for proposals.
[5:46 PM] Tron: Yes.  Still President (unpaid in 2022).  Because the Ravencoin Foundation is voluntarily supported, I want the original funds provided by Medici Ventures to continue to support nodes, monitoring, e-mail, etc.  New projects/proposals/grants will be financially supported by the community on a project-by-project basis.  I make myself available for things like the Bittrex node support, or helping to educate about Ravencoin and assets.
[5:52 PM] BadGuyTy: ok well this week I hope to have squawker seo on google finally and the I will try to get started on the js provider was working on a rip11 in browser decoder but as it seems that moontree won't be releasing with a provider I will be making one for them I guess,,, @Mango Farm would be happy to also have it work with your wallet if you have a list of endpoints to call for each of the needed actions.
[5:54 PM] Mango Farm: That's great Ty.  We ditched the RIP11 interface in the last update and haven't added it back yet.  The UX we had was wonky and I wanted to refine it before adding it back.  Definitely would like to work with you on this.
[5:54 PM] Mango Farm: First up is our new UI refresh (which is pretty cool), then finally Ice Wallet out, then we will have time.
[5:55 PM] Mango Farm: AlphaBeat helped a lot with the starting point for a really nice UI for what we can finally call Mango 1.0 coming out in the next couple of weeks
[5:57 PM] Mango Farm: It's awesome for me to see someone integrating RIP11.  Really happy you are doing that.
[6:18 PM] BadGuyTy: yeah i mean its where the use case of squawker really takes off. i mean messaging is nice and all but buying and selling digital stuff thats money making tech right there
[6:46 PM] kinkajou (SegWit Clique): Channel closed. Great meeting, thanks for coming everyone.
----------
[4:00 PM] kinkajou (SegWit Clique): Channel open
[4:06 PM] kinkajou (SegWit Clique): @Tron were you able to get in touch with Bittrex at all?
[4:12 PM] Seal Clubber: Yeah they are down for like 4weeks now
[4:17 PM] Tron: Yes.  I have an open Slack channel with them now.  I sent them the information they need.  They thanked me.   That was on May 20th.  I have not heard anything since.  I just verified that Deposit/Withdraw is still inactive.  I asked (via the Slack channel) if there is something wrong, or if there is something I can do to help.
[4:19 PM] Seal Clubber: Thankyou
[4:27 PM] kinkajou (SegWit Clique): Yes, thank you @Tron !
Has there been any more discussion with regards to P2SH? I know we don't have much of the community in here but I think it's highly preferable to see if there is a compliant workaround to the auditability issue.
[4:31 PM] Tron: I haven't done anything this week on it.  I'm working on Foundation taxes.  Mining donations are great, but they came in so many small transactions at so many different times, that I need to write some scripts to be able to convert the information into usable info for the 990 tax form.
[4:35 PM] kinkajou (SegWit Clique): Is there anything that we community members can do to help test this? Just trying to get an idea of what exactly is needed to determine the viability of a proposed solution. Is it a matter of having the entire supply auditable? Or is it a matter of matching the supply to a specific address? A combination of both or would one suffice? Compliance can be quite confusing I guess I'm just not sure what exactly would merit a workable solution
[4:39 PM] Someone_2: Was LSJ10 something's solution viable?  He posted something but I don't know that it was 'sanity' checked.
[4:40 PM] Tron: To test it, use Testnet with P2SH activated, create an asset, then send some of that asset to P2SH transaction.  Then either use the audit script in https://github.com/RavenProject/Ravencoin/blob/master/assets/tools/asset_audit.py to see if the asset passes the audit.  And/or use the rewards RPC calls to make sure it accounts for all the assets, and that the P2SH ones aren't unaccounted for.  And check the asset explorers to see if the amount in various addresses add up to 100% of the issued asset qty.
[4:42 PM] kinkajou (SegWit Clique): @LSJI07 ? Link to the proposed solution? I must have missed it
[4:43 PM] Someone_2: It was basically a logic check.  I'm not easily finding the post.  It wasn't a link.  The main concept was to differentiate things against P2SH by noting the multisig aspect.  Meaning, if it's multisig, it's P2SH.  I wasn't entirely sure what was meant, it was kind of messy.
[4:44 PM] Someone_2: I think I'mf inally grasping the main issue better however.  the problem is to make sure that the P2SH stuff is accounted for in an audit.
[4:48 PM] Tron: The trick with P2SH is that it could be anything - you could not know that it is a multisig.  The transaction COULD be multisig -- you can only see the hash of the script - not the script itself.
[5:28 PM] Blockchain John: @kinkajou (SegWit Clique) Channel is still open.
[5:37 PM] kinkajou (SegWit Clique): Going to close the channel now. If any @Core Tester are available to help with testing P2SH (https://discord.com/channels/429127343165145089/482289959261175838/979846492846174270) this week DM or ping me in testnet

Any ideas when RavenCoin will be back on the exchanges for trading?

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]