- Yep, I'll set. - I should. - Okay.
All right, so we are recording, we are online and don't see a ton of people in here with us, so we will just dive into it. We are recording this so folks can follow along at their leisure, so we'll keep that in mind. And with that, as our
purpose. I will welcome everybody, including my colleague John Nash and all of our redheads to our first event in actually quite some time. We're going to be talking today about our newly being released. We've been working on
it for quite some time as you guys all know. The 4.22 wallet features what we built into it and why we'd taken the time that we had. We are going to keep this as high level as we can really to just share a bunch of information about what we built. We will be digging in
into the details more in depth. We plan to hold sessions like this, whether on Twitter or likely on Reddit as well very soon. Live discussions of sort of what we're doing just to give an insight into what the team's up to and where our plans are. We've not stopped working despite the crypto winter and the
the scary news headlines with FTX and the rest of them. And that's one of the things we wanted to share with the community and let you know we're still working hard. So diving into the content then, and I'll turn it over to John momentarily as he's been the prime mover and heavy lifter behind this work.
Along with a couple of other developers and their skill sets, but John truly deserves the lion share the credit here. So I'll do the intro and let him share the Waiter of the details. So we did adopt bitcoins was zero dot 22
it's now term 22.0 same code. That was released in 2021 by the Bitcoin core folks with a lot of features, a lot of technology, tap routes, one of the buzzwords that people have talked about and will share a bit of that. But that is where we've landed at this point with the Bitcoin code.
that we're following along with our of course red coin consensus and staking and POSV version 2. We have some complexity in some of the ways that some of these features need to be activated and we'll definitely be spending a bunch of time writing and talking about that but for the sake of just keeping
short and sweet. Look for those updates shortly and we are activating that as part of this new rollout with .22. That puts us in a very good position for the future with a lot of capabilities including some of the stuff that we'll speak about on chain atomic swaps and integration
with other systems, Dex's that we're able to really broaden the ecosystem. So, all told it is some great work. One note, the new Mac OS version of the wallet is likely not going to be compatible with Mac OS's prior to 10.14. That's not something we can control. It's a
and trying to stay in support of all the various OS, really architectures and changes. So older version three wallets will still work with older Mac OS's. But if you're running an older version of Mac, just be aware when you go to upgrade, you may have some problems.
We've also included in this as a part of the technology, although we are not objectively supported by hardware wallets that are out there ledger and those like them. This wallet release for us does enable hardware wallet support, so we can get the code of
adapted or I'm sorry adopted by folks like Ledger or keep key or some of the others and we actually have a live full request waiting and at least one of those we will be able to use hardware wallets to backup storage and keep things safe and secure. It's a great step forward and one that's been a bit coming.
We've also added as part of the Bitcoin Core work, or RedCoin Core work, sorry, is apting Bitcoin Core. Something called I2P or the Invisible Internet Project. That's an encrypted network. It's an alternative to Tor. If you're familiar with that, the Onion Router, it's an option if you choose to
run it, but it really is a fairly complicated concept if you're not familiar with it. The wallet does however allow native connections to both of those encrypted and arguably more secure networks. We will be documenting that as we can and you know if you do choose to use that, feel free to add some documents yourself or
reach out to us and put a walk through together because that stuff is important in certain roles and certain situations to be able to hide your traffic. And then I mentioned also taproot features which really the absolute bullet points to know about that.
It will simplify transactions structures and add to a bit of network efficiency, which allows us to fit more transactions without making changes to the network. Higher data density added privacy and simplifying some of the more complicated transactions that may pass through our network, something called
It's called snore signatures that is a great word just to say. So that's why I put it in. But it is a factor in the technology here of TapRoot and the smart contract and ability to add some logic and some automation to what's happening with Redcoin and frankly with Bitcoin as well.
I will turn it over to John at this point. John's done some extensive work on, well, everything, but I'll let him start with the new build system and the process we built. John? >> Good afternoon, everybody. Thanks for the intro. Welcome, everybody.
I hope you can hear me okay, I'm gonna push a little bit of background noise around me today. You're great. Sounds good, that's the noise filtering that we're plugged in these clients now is fantastic. So really I wanted to, let's look at everybody update on
on where the one with the ZAS and what we've been up to and why not taking so long and I guess anybody who does follow on our development through various sources through GitHub or some of the GitHub Connect and Apps, they're a Discord channel, like, sexual, C. Sometimes we have sporadic periods of quietness.
So there's a whole flurry of commits come true and that I guess really demonstrates the whole development cycle of making changes and testing and retesting and rechanging and building this wall out. As I alluded to, we have taken our red coin
While our previous version of version 3.10 and extrapolate out all the elements of red coin, you'll layer that on top of Bitcoin.2.2, which really fast forwards us a lot of the blockchain
is components that we have been waiting for for quite some time, excuse me, I'm bringing that forward and really modernizing the wallet. And a whole bunch of other technical improvements, you know, the behavior performance of the wallet is also
increased dramatically. There's a few key points that we've introduced some new features so the new wall looks slightly different to the previous where we're brought in things like so just giving an estimate of time for staking there's a whole
table of where to expect stakes to occur on what available inputs that you have. So that's kind of interesting. From a user point of view, don't sort of know where your list of coins sits in the next
I'm not going to go through in any particular order. I think we've got lots of cool stuff that the mallet is going to bring. So I'm just going to work through this stuff that comes to my mind and I'm sort of juggling down here and notes. One of the key
points I guess that we've struggled with or what, use the struggle with is back out wallets. I think that's always been a challenge particularly if you are staking because it does generate a lot more transactions in your wallet than perhaps it just has normal standard wallet. And back out the wallet dot that far has always a
you know, from our user point of view, Trumblism and difficult. What we've done is actually implemented in both our BIP 39 and BIP 44 support into our core wallet. So now we support not
just 53, too, which is a HD wallet, which is standard for Bitcoin. They introduced that quite early on, I think it was about version 15 of their wallet. But you still require the backup of seed phrase, I mean, I'll be import of seed phrase, which is a long character string.
What we introduced was bit 39, which is the WC phrases. So we can use a number of different lengths of C phrase. So that is your C phrase on the Monika, another 7-old year for that. So the 12,
of 15, 18, and up to 24 words that as a user you can have randomly generated or you use your own from selected from the list of available words and generate your own seed phrase that you can write down store, backup, and be able
to resolve that in a later date. The wallet will scan the blockchain for the transactions and keep track of the various change and main addresses for you. I'm obsessed with BIP-9.
44 was an additional step that we put in place where we're supporting the actual coin. So the specification adds a coin purpose there of 44 and then in the way that it's generated we also have support for our red coin on that
So if you're using, for example, someone like Coinome who is another wallet that supports Bit44, you could actually import your addresses from other wallet supporting Bit44 into your core wallet. So that's kind of an interesting
way of using it and certainly for people in the past who have used their game back to our browser extension or some of our recent work on mobile wallets or supported bit 44, you should be able to find an easy way to either
transfer your funds from one more to another without actually having to do a transaction you can just load up your seed price and it will go off and do a discovery. The core wallet actually supports multiple wallets so in your in the conversion version 3
There's one wallet only and if you want to load up a different wallet there's a few steps you have to go through to support that. In the claw wallet now you can support multiple or create multiple wallets and list those transactions and etc. and use each wallet independently of the
is one caveat on that. The wallet only supports staking from one wallet file at the moment where we're working on in a future with kickboxes. First round of changes, we're actually working to develop support staking across all wallets.
So, yeah, in version 422, just around the wallet architecture, lots of changes there to make life easier for users to manage their families.
So you can load up one or two wallets if it's a personal use in business, for example, just the argument set. You have both your wallet, fair and transact to and from. In addition to the actual wallets, where we added some RPC calls in there to be able to manage
So from the CLI or from the console, we can, or as a user you can, dig in the decals and back up your seed phrase separately as a dump file or get the seed phrase and the money phrase out as a piece of text and say that somewhere secure.
I was probably about it, just the wallet components. Next thing I want to talk about, what's being delayed, I guess, is getting the wallet and we're just reaching the conclusion now is just around versions signaling on the blockchain.
change version signaling. So for those who are a little bit tech-n-reaware about what makes it a block change, so the block chain has gone through a number of different versions, changes over the years since we first kicked off and we're now running a block version 5 for our blocks. And that
the number of changes of PLS, switching to PRS, implementing BIP66, implementing PLSV2, which was the developer funding. And now as we move forward with version 4.22, we're switching our
block chain versioning to version bits which is a very different structure and so being a block version 5 it'll be much larger number where we can turn bits on and off to stipulate features that will be incorporated. So the first two features we're going
to incorporate a two that were skipped over in initial builds, whether being the height in coinbase. So what we're doing is take a natural, when you stake a block for what you're just taking for your coin generation, it will store the block that you're
generating in the coinbase as a record. And the goal there is to reduce any chance of duplicity of transactions and staking. The second one we are implementing is CTLV, which is a time lock. Check time locks.
which is quite important for us to get across to some of the development that's occurring on cross-danked swaps. Yeah, probably swaps feature that was actually shortly after Bitcoin 12, it was implemented
shortly after we had our work on our original switch to the Bitcoin's codebase. So in a two relatively simple change in the blue, using VirginBits or using the Bitcoin's version, it's actually easy to track and manage the outcomes
So we set timeframes. The other cool thing is about that you don't have to do one change after another. You can run a number of configurations or changes that you want on the blockchain to occur over
lap in a parallel situation, which again from a time wise point of view as we're moving forward, bringing red coin up to specle up to speed, modernizing, we need to enable some of these features. In a timely fashion, I won't say quickly, we're trying to state it so that not everything will be
on day one we're going to kick off first to the height and coin base in the CTLV. In our release that we put out, make public in our first release candidate when people state those two features will be enabled and being validated on the blockchain.
Following that there will be things like Segway and Taproot and the CSV that will come along shortly thereafter. We will be managing and watching that progress. We will deviate a little bit from what Bitcoin did in their time frame.
how many blocks to look at. We have extended the time period so it's a moving target of a block of 10 days so basically we need about 90% locking over a period of 10 days of staking. And there's a few people who are staking who contribute towards that if you're in a static while it looks staking.
then you're not contributing to the activation but your wallet will switch over. At some point in tech you're alluding to some older versions. Just like previously as the blockchain moves forward some of those activations will become
locked in and effectively people will need to move forward to operate to make sure that they're current. Which is a great segue into another feature that we implemented early on in the initial switch over the quarter three two and that was actually having the core wallet
go out and check GitHub and verify the version that was running versus the version that was developed on GitHub and being able to notify users that there is a new version. Are they running the most current version? That could be switched off and off. Obviously not everybody wants to be bothered by notification.
But certainly for people who want to be aware of new versions being available, the wallet will now display a banner, a splash banner, when it first launches, along with a little flag inside the GUI to see the flag.
that and also this RPC commands too to be able to pull that information out if you look at blockchain, I think it's get blockchain info off the top of my head, we'll display that warning message in there as well if you need to do an upgrade.
What else do we do there? There's been lots of improvements around peer management, so I know we have a few clients still sitting up there, but they actually forked off, but they still hang around loatherly on our networks and old version 2, which are not compatible with our current blockchain, but they do.
come along occasionally and noise with their way to update but they can't that you really just got up going upgrade but now with pre management we can ban them for periods of time and such from the from the GUI you know so you know as a cello CLI slash RPC command
What else in the, for users we have added some social links. So from the GUI we can select from one of the menu options to browse out to a relevant red coin centric.
When pages just read it as a point of reference, what else are we going on there? I think the only thing that you didn't touch on it, it probably just to just to
kind of reach out to some of the more technical folks that are going to be listening to this. If you want to talk a bit about the continuous integration building in. Yep, that's a good point. I guess one of the things that we've been, I actually got a couple of things we've gotten building, not just a continuous integration, but more of
What is the build system? Because Bitcoin have been, that worked very hard to evaluate that build, the make sure that builds are not corrupt or not compromised unless this is the best word. So when somebody builds the wallet
for distribution, they basically take a charm 56 value of the bill and lots of comparisons and the ones that are always compares and as equal, then I'll push that out to the public repository. The part that bill system
I've never just modified in the last couple of years to use a thing. Not sure what the pronunciation of it is, I've got it says UX, GUX, GUIX. It's a nice automated tool to build up in a sandbox environment using pretty
term and binaries. It's a little bit like previous, but it takes a lot of manual hand holding that would occur to build off a bunch of different binaries. And now the actual binaries are building.
is getting a lot more extensive with covering a lot more architecture from the standard Linux, not just from the OS's Linux and Windows and Mac OS, but also some hardware platforms such as PowerPC and Raspberry Pi's.
Yep, and the work that goes into that even though people take it for granted again, it's notable, you know, that as a small team kind of working at our best effort here, we do have coverage on most of the major platforms and operating systems and I will say again that the folks running these
older macOS needs to upgrade but the truth is if you're if you're not really at the current version you probably should upgrade there's a lot of you know as we've talked about there's a lot of new stuff in the new wallets including efficiency less resources being used that's always great I did just want to touch on a
couple of things, some that the John mentioned, but just to highlight how really kind of game changers there are. The ability to run multiple wallets for you to have, you know, sort of a business red coin wallet and a personal red coin wallet or maybe one for your your content rewards and one for
staking, you know, a more substantial amount of red coin. That's obviously the usability factor. It means a lot to us. You know, we've heard a lot of people say we'd like to be able to do that. It's not as easy as just saying, okay, here you go. You can, but we've gotten to that point. So you are able to,
simultaneously have multiple wallets open within the same piece of software. And again, as John said, with the seed phrases, anybody that's been in the red coin space for a while or really with any desktop wallets that are using that wallet.dat file format, you're very familiar with having to back up
that file or move it around to new computers. Using seed phrases is essentially a complete replacement for that. You don't need to back up a wallet.dat file ever again. You just need to write down your ever so important seed phrase, stick it somewhere safe. If anything happens, type it back in and
Let the blockchain rediscover your assets. That and interoperability with other wallet, right coin, home, or guarda, and some of the others that are about to come out. Really is a cornerstone of giving our red head users the options to use a lot of the popular wallets as
best we can and to hear to those standards. That's something we thought pretty hard to get into place. There will be a little bit of confusion with how to use seed phrases, particularly migrating old wallets and we do want to make sure that everybody knows what's happening as they upgrade. So if you do have any questions as you're using the new software, please give us
So shout, you know, ask a question in one of our channels, Reddit, Telegram, Twitter, wherever it might be, or email help@redgoyne.com. And just as a benchmark of the performance aspect of this wallet, which we are pretty proud of at this point, again, we're one of the oldest legacy
blockchain projects we've got almost eight years of data on our blockchain at this point with the latest actually the version behind the latest Although we haven't changed that code so it should be exactly the same It took for an 11th month set of testnet data so about an eighth of our large
our actual main net is full data sink completed in 29 minutes. So that's about half an hour for 11 months of data under very good conditions and that means that again if you start from scratch launch the wallet it'll give you a nice informative screen with what
your things speed are and what's happening. That also is a nice little addition to the wallet where it just sort of seemed to hang before. But you'll see exactly what's happening and you can expect with good network conditions to sink certainly four to six hours is reasonable, maybe a little longer depending on your setup and your
you a memory but not longer than that and certainly not the days that it has taken in the past. So we are very much glad of that. There's also, and again, minor changes sprinkled in with the major changes here. If you're running the client in Tefnet mode now, you'll see an inverted color scheme.
just to alert you that you're on testnet. We've done stuff with font handling that caused us lots of grief back in the day with the Catalina upgrade on max where it basically ate our phone description. So that issue of can't see the text in the wallet anymore should be gone for good across all
platforms. That is a function of what Bitcoin actually upgraded to in our adapting that. So who knows to them. And I think for the most part that that covers a lot of it. The, I think the only thing that was really left for me to turn back to to John unless
you wanted to talk more in detail about some of the under the hood stuff. I know we're committing it'll be available for public download by the end of this week or thereabouts. You can find the compiled software at download.redcoin.com. You can find the source code if you want to
build it yourself with the new build system John just described. Or if you'd like to contribute to it, you can check out our get up same thing. Source code is available there. Bineries will be available there as well as download.radquaint.com. And that being said, I think that
It's a lot of work that, you know, someone that's going to go unremarked because it just works and it does what it's supposed to. But if you look into the notes and especially again, an appeal to the developers and the coders out there, we absolutely want you guys and girls to join in and to help us do more of this.
bottleneck by the people that we have and the resources and time and you know only so many awake hours in the day but realistically you know it's a labor of love so anybody that wants to join in is always welcome here and with that I guess I'll turn it back to
And John to say a little bit of wrap up. And I do want to thank everybody for joining us on our first Twitter Live effort went pretty seamlessly considering and we'll be doing these on a regular basis as well as on some other channels really just to keep the community redheads informed as to what's going on.
John, you want to? Yes, sorry, I was having a little hit by a call there before, but I'm sorry just to wrap up where we are, at least for this session. I have to say really excited about this particular version. It's been a long time coming, really.
personally and also from a project point of view as Tec was alluding to we are a small development team it is a labor of love and we do from what the love is this project and we are trying to make exciting stuff happen but more hands that again
involved at different points. You don't necessarily have to be a code of code as you could be somebody who has identified some documentation that needs updating or needs to platter out it. All those little bits, you know, they all do hope. Many hands make right work. There's
It's always something to do somewhere and a lot of reach out and get involved. 4.22, this will be our first release candidate. The monster number of alphas and releases over the last eight months or so for people to play around with.
with and I'll get into that capital point as well. Moving to a release candidate. It's always used with a error caution. You have to be aware that we do our best to get code clean and
As safe as possible, Ebo, who has known me over the years, is what people's funds to be safe and it doesn't matter what value to lose something big or small as this painful. So any feedback that people have is more than welcome. We've already had a couple of poor requests thrown at the
repository to have some fixes done, mostly cause many, but those are all things that help to identify what needs to be done. Timing wise, as Cacallu too, end of the week, what they're about, we are the last bits of writing up a release
and getting those things together, a few little code changes I'm still working on so to push out there and yeah, we'll love to get it in the hands of people to actually start using and testing. More or less, just using and giving feedback.
I saw that from a development point of view have been staking on both main and testnet using the code changes that we are going to be pushing out to you guys. So it's exciting. There are lots of steps we came from Bitcoin version 10, we're now at Bitcoin version 22. So to get
the significant number of changes, hence we've spent a lot of time trying to get things as close as possible as possible to what you're used to as far as the way ReCoin operates, incorporating the changes from Bitcoin into that.
I think our users will generally be quite happy with what would be it all to produce and have a good user experience. And I guess that's really what we're looking for is a great user experience. Crypto is not easy by any long shot. When you get away from the trading game that we've
We were sort of used to hear about the news and the dictation of price, but the fundamentals, the way that crypto is supposed to work and how do we work and how do we use it as a P2P environment. That's where we're coming from as a team, getting back to that
as crypto fundamentals and using crypto as a true peer-to-peer payment and providing the tools to do so, whether it's a desktop wallet or mobile wallet and even things such as kipping and low-tracking.
transaction fees, no transaction fees across social networks, although we're trying to push our focus and remain the price remaining off the table. Absolutely. Thank you, Jim, for that.
That's probably a good place to leave it that that really is the focus of the project. Pretty much always has been and as we've always thought if the values there the applications are there and we are still building on that front. That's a little bit beyond the scope of this particular talk but we'll be sharing a bunch of that information as we're able
to incoming talks and coming events. We haven't lost sight of that either that our existence, our red coin sort of use case is that ability to share payment, to share value for content, for good solid information that people have created that deserves rewards.
As John said, it's not about the trading aspect. It is, to a very large extent, about creating those tools. And I think the redheads will be quite happy with what we've been up to as we start to expose it. And again, just a final appeal. We are always looking for volunteers if you are interested.
I just did not know. I just did not know. I just did not know. I just did not know. I just did not know. I just did not know. I just did not know. I just did not know. I just did not know. I just did not know. I just did not know. I just did not know. I just did not know. I just did not know. I just did not know. I just did not know.#
in reality and document them, the more successful it will be. It is absolutely a community effort. So don't hesitate, join the group, we're kind of fun. And I guess that's it. Thank you very much, John, for your insight and your amazing efforts in all this with the wallet. And thank you to the Redheads who joined in.
and those listening later on. Stay tuned for our next one and you know the standards, smash the follow button and the likes and the retweets and genuinely the more exposure we get, you know, again the more successful we can be as a community. So thanks everybody and have a great evening. Yes, thank you everybody.