Gridcoin "Fern" Release
Finally! After over ten months of development and testing, "Fern" has arrived! This is a whopper. 240 pull requests merged. Essentially a complete rewrite that was started with the scraper (the "neural net" rewrite) in "Denise" has now been completed. Practically the ENTIRE Gridcoin specific codebase resting on top of the vanilla Bitcoin/Peercoin/Blackcoin vanilla PoS code has been rewritten. This removes the team requirement at last (see below), although there are many other important improvements besides that.
Fern was a monumental undertaking. We had to encode all of the old rules active for the v10 block protocol in new code and ensure that the new code was 100% compatible. This had to be done in such a way as to clear out all of the old spaghetti and ring-fence it with tightly controlled class implementations. We then wrote an entirely new, simplified ruleset for research rewards and reengineered contracts (which includes beacon management, polls, and voting) using properly classed code. The fundamentals of Gridcoin with this release are now on a very sound and maintainable footing, and the developers believe the codebase as updated here will serve as the fundamental basis for Gridcoin's future roadmap.
We have been testing this for MONTHS on testnet in various stages. The v10 (legacy) compatibility code has been running on testnet continuously as it was developed to ensure compatibility with existing nodes. During the last few months, we have done two private testnet forks and then the full public testnet testing for v11 code (the new protocol which is what Fern implements). The developers have also been running non-staking "sentinel" nodes on mainnet with this code to verify that the consensus rules are problem-free for the legacy compatibility code on the broader mainnet. We believe this amount of testing is going to result in a smooth rollout.
Given the amount of changes in Fern, I am presenting TWO changelogs below. One is high level, which summarizes the most significant changes in the protocol. The second changelog is the detailed one in the usual format, and gives you an inkling of the size of this release.



Note that the protocol changes will not become active until we cross the hard-fork transition height to v11, which has been set at 2053000. Given current average block spacing, this should happen around October 4, about one month from now.
Note that to get all of the beacons in the network on the new protocol, we are requiring ALL beacons to be validated. A two week (14 day) grace period is provided by the code, starting at the time of the transition height, for people currently holding a beacon to validate the beacon and prevent it from expiring. That means that EVERY CRUNCHER must advertise and validate their beacon AFTER the v11 transition (around Oct 4th) and BEFORE October 18th (or more precisely, 14 days from the actual date of the v11 transition). If you do not advertise and validate your beacon by this time, your beacon will expire and you will stop earning research rewards until you advertise and validate a new beacon. This process has been made much easier by a brand new beacon "wizard" that helps manage beacon advertisements and renewals. Once a beacon has been validated and is a v11 protocol beacon, the normal 180 day expiration rules apply. Note, however, that the 180 day expiration on research rewards has been removed with the Fern update. This means that while your beacon might expire after 180 days, your earned research rewards will be retained and can be claimed by advertising a beacon with the same CPID and going through the validation process again. In other words, you do not lose any earned research rewards if you do not stake a block within 180 days and keep your beacon up-to-date.
The transition height is also when the team requirement will be relaxed for the network.


Besides the beacon wizard, there are a number of improvements to the GUI, including new UI transaction types (and icons) for staking the superblock, sidestake sends, beacon advertisement, voting, poll creation, and transactions with a message. The main screen has been revamped with a better summary section, and better status icons. Several changes under the hood have improved GUI performance. And finally, the diagnostics have been revamped.


The wallet sync speed has been DRASTICALLY improved. A decent machine with a good network connection should be able to sync the entire mainnet blockchain in less than 4 hours. A fast machine with a really fast network connection and a good SSD can do it in about 2.5 hours. One of our goals was to reduce or eliminate the reliance on snapshots for mainnet, and I think we have accomplished that goal with the new sync speed. We have also streamlined the in-memory structures for the blockchain which shaves some memory use.
There are so many goodies here it is hard to summarize them all.
I would like to thank all of the contributors to this release, but especially thank @cyrossignol, whose incredible contributions formed the backbone of this release. I would also like to pay special thanks to @barton2526, @caraka, and @Quezacoatl1, who tirelessly helped during the testing and polishing phase on testnet with testing and repeated builds for all architectures.
The developers are proud to present this release to the community and we believe this represents the starting point for a true renaissance for Gridcoin!

Summary Changelog



Most significantly, nodes calculate research rewards directly from the magnitudes in EACH superblock between stakes instead of using a two- or three- point average based on a CPID's current magnitude and the magnitude for the CPID when it last staked. For those long-timers in the community, this has been referred to as "Superblock Windows," and was first done in proof-of-concept form by @denravonska.







As a reminder:









Detailed Changelog

[] 2020-09-03, mandatory, "Fern"





submitted by jamescowens to gridcoin [link] [comments]

Mousecoin Network May 2020 Report

Mousecoin Network May 2020 Report


The last month in the world of Mousecoin has been HUGE! There have been many changes, the addition of new awesome ways to earn MIC3 including our Faucets page and the Phoneum Games. We have also seen the launch of our Community Membership, which entitles each registered user to receive up to 200,000 MIC3 per month. We hope you are all keeping safe and are happy to provide you with our Mousecoin Network May 2020 Report.
FINALLY, after months of negotiation and with the help of Phoneum, Mousecoin has partnered with Phoneum to be included in two of the most popular Phoneum crypto games currently available. We have added a new Games page, whiche features all the information and link for the games, with more to come. Here is the run down:

Crypto Treasures

📷 📷

Crypto Treasures is a game, where players complete various quests, trivia and mini games to unlock Gold (in-game currency), Treasure Chests, Items, Collectibles, and various Crypto currencies, including the featured Mousecoin (MIC3).

Crypto Planet

📷 📷

Visit a new type of planet, one that allows you to earn real cryptocurrencies while playing a beautiful and futuristic game. The main objective is to extract the valuable resources of the planet: Crystals. There is a special machine designed specifically to dig up the Crystals automatically and deliver them to you. All you have to do is activate the Digger and after 4 hours, it will have the resources ready to be claimed.

Earn up to 200,000 MIC3 Per Month!

At the beginning of last month we began establishing our Community Membership which offers all registered Mousecoin Members a share of the rewards earned from the Community Fund just for being a member and following Mousecoin on all of our social media. As we come to the end of the first month we are currently in the process of checking all registrations and working out payments. We have also updated the profile page to include a Member News tab, Verified Notifications for each Social Media and a Monthly Payment History section. We are currently working on verifying all accounts registered before 1/6/2020, and should have all of these processed in the next few days, with all payment going out before the end of the week.

Become a part of the Mousecoin (MIC3) Community.Membership is FREE and it comes with HUGE bonuses!!

Our Community is important to us, it is the backbone of the Mousecoin Network. Every follow, like, interaction, comment and re-post of our content members of the Mousecoin Community do all helps us to grow awareness of Mousecoin, growing and strengthening our community. To show our appreciation for your loyalty we are rewarding every Mousecoin Member with a regular monthly payment of up to 200,000 MIC3 just for joining and remaining a member of our social media(s). To become a member all you need to do is complete the registration form below, making sure to become and stay a member on our social media(s) and start EARNING!!! Each of our social media accounts (listed below) that you follow entitles you to a portion of the potential 200,000 MIC3 you can earn each month. If you only follow on Twitter, you will only get 25,000 MIC3 per month, follow on 2 socials and get 50,000 MIC3, etc.
TELEGRAM Become and stay a member of:
Get 25,000 MIC3 PeMonth
TELEGRAM ANNOUNCEMENTS Become and stay a member of:
Get 25,000 MIC3 PeMonth
DISCORD Become and stay a member of:
Get 25,000 MIC3 PeMonth
TWITTER Become and stay a member of:
Get 25,000 MIC3 PeMonth
FACEBOOK Like and Follow:
Get 25,000 MIC3 PeMonth
REDDIT Become and stay a member of:
Get 25,000 MIC3 PeMonth
MEDIUM Become and stay a member of:
Get 25,000 MIC3 PeMonth
INSTAGRAM Become and stay a member of:
Get 25,000 MIC3 PeMonth
PLEASE NOTE: You must register before the 1st of each month in order to qualify for the previous months payment. All payments will be processed in the first week of the following month, once the accounts have been verified. You can check the process of you social account verification’s, as well as your monthly payment status on your account page. You must remain a member of the social media to receive the reward.
For anyone that isn’t already a member, you can find all of the information on our Community Member Registration Page
Just a reminder for the community and also for any new members, we have added a Wallet Setup Guides page, which takes any first time user of Mousecoin step-by-step through the process of installing their Mousecoin wallet and getting it online. The guide uses the latest blockchain snapshot found on the Wallet Downloads Page in the example explanation meaning that all new members of the Mousecoin community will be able to get their wallets online faster as the sync time should be minimal. We will be updating the blockchain snapshot at least once every month to ensure that people have access to the most up to date blockchain info. The latest blockchain snapshot was performed on the 1st June 2020.
The wallet version is currenty V1.0.0.0, with future releases of the Mousecoin wallet coming soon
If you are new to crypto currency or just after a bit of guidance setting up the Mousecoin wallet, check out our Wallet Setup Guides
📷 Windows
📷 Raspberry Pi
📷Wallet & Blockchain Snapshot Download (UPDATED 01-06-2020)
In the last month we asked the community if they would be interested in being a part of a Community Staking Pool. After investigations into this finding security flaws in most platforms, as well as the lack of interest from members of the community we have decided to not go ahead with the Community Staking Pool. While we understand that there are members of the Mousecoin Community that are unable to stake themselves for whatever reason, and that there are a number of staking platforms that offer pool staking for MIC3 to help these people stake, we will not officially be supporting any staking platforms. We ask all Community members using these or thinking about using these to keep in mind that any MIC3 hosted on these platforms is not in their wallets, and therefore not controlled by them. Do proper investigations into any platform that you use for this as there is always the possibility of loss. We encourage all members of the Mousecoin Community to stake from their own wallet (where possible) as this helps us to secure the network. If you need help setting up your wallet, go to our Wallet Setup Guides page for step-by-step guides on setting up your Mousecoin wallet.
We have updated the Mousecoin (MIC3) Faucets Page:
To make things clearer and we will be adding more faucets soon!
Last month we saw the edition of the USDT/MIC3 pair to nanu exchange. In our efforts to increase exposure of Mousecoin, we are still attempting to list on both ATAIX and Unnamed.Exhchange.
ATAIX We have risen to 18th position in the voting list on ATAIX, but we still need your votes. Remember you can vote every 24 hours for this listing, and you can share in 125,000,000 MIC3
Unnamed.Exhchange The exchange listing for Unnamed.Exhchange is 0.05 BTC. For anyone unfamiliar with the exchange there are two ways that you can donate to the listing:
1. If you are already a member of, or wish to be a member of Unnamed.Exhchange (and why wouldn’t you), you can put funds towards our listing by tipping us through the trollbox (Mousecoins). If you wish to be a member of Unnamed.Exhchange, you can register here:
2. You can also donate to the listing fee through the following addresses: BTC – bc1qmaqzhfqcw0urva0rtgfz5qvq4rw7kdnp6j7754 LTC – ltc1qc775eeftdde2jrevnyukrd2w9853jy5gmtv6rn DOGE – DEnBpriaFnKiNeBv6Q7MVxMg5hLv5urQFg UTIP – AUTyu2JhGAaCkM3KAmeBopto2bNBchNJfE
If you would like to donate in another crypto available on Unnamed.Exhchange, we have opened up the chat on the Discord channel HERE to assist with this. Please request the address and we will provide it for you. ANY AND ALL DONATIONS ARE WELCOME!! This is a good exchange and getting a listing her should help lift the profile of MIC3.
We will be reporting balances to the discord channel
In the last month the Community Fund has undergone a huge amount of change. We have completely moved all of our remaining balances away from 4Stake, with the MIC3 going to the Community Fund MIC3 account and the remaining crypto’s towards out listing on Unnamed.Exhchange. The Community Fund page on the website has also been updated to reflect all of the changes. It is an exciting time for the Community Fund as we have now reached a balance that will sustain itself. This is why we have introduced the Community Member payment, and are able to sustain the faucets we have on and in the Phoneum Games. There is still more to come!


📷 📷📷 📷📷📷📷
📷 📷📷


📷📷📷📷📷📷📷 📷 📷📷


GENERAL: Wallets Explorer Github About Staking
NEWS/UPDATES: BitcoinTalk Discord Telegram Mousecoin Official News Twitter Medium
COMMUNITY FUND: Telegram Facebook
SUPPORT: Discord Mousecoin English\_ENG
FACEBOOK: Mousecoin English Mousecoin Portuguese
TELEGRAM: Mousecoin English\_ENG Mousecoin Portuguese Mousecoin Russian Mousecoin Korean Mousecoin Spanish Mousecoin Australia\_Australia


submitted by Micmouse to u/Micmouse [link] [comments]

HELP! OverflowError: timestamp out of range for platform time_t

I am guessing this means Electrum Wallet is set to a particular time zone, which is not allowing me to send bitcoin. As I tried to send to the exchange and found this error popped up. This is my first time using the wallet and I have no idea how to change the time to sync.
Anyone have an idea what I can do to change it(thats is it is the time issue) so I can send to exchange.
Traceback (most recent call last): File "/home/dotbin/electrum/electrum/gui/qt/", line 1542, in do_pay self.do_pay_invoice(invoice) File "/home/dotbin/electrum/electrum/gui/qt/", line 1555, in do_pay_invoice self.pay_onchain_dialog(self.get_coins(), outputs) File "/home/dotbin/electrum/electrum/gui/qt/", line 1591, in pay_onchain_dialog external_keypairs=external_keypairs) File "/home/dotbin/electrum/electrum/gui/qt/", line 1617, in preview_tx_dialog window=self) File "/home/dotbin/electrum/electrum/gui/qt/", line 690, in __init__ finalized=False, external_keypairs=external_keypairs) File "/home/dotbin/electrum/electrum/gui/qt/", line 126, in __init__ self.add_tx_stats(vbox) File "/home/dotbin/electrum/electrum/gui/qt/", line 634, in add_tx_stats self.locktime_e = LockTimeEdit() File "/home/dotbin/electrum/electrum/gui/qt/", line 32, in __init__ self.locktime_date_e = LockTimeDateEdit() File "/home/dotbin/electrum/electrum/gui/qt/", line 155, in __init__ self.setMaximumDateTime(datetime.fromtimestamp(self.max_allowed_value)) OverflowError: timestamp out of range for platform time_t
Additional information
submitted by unusual_characters to Electrum [link] [comments]

[PSA] Dogecoin Wallet version 1.4 released. You must update.

WARNING: DO NOT send your wallet.dat file or dogecoin folder to anyone. There have been reports of people offering to help others by asking them to send their files to them so they can help. DO NOT do this. Scam attempt picture
Always encrypt your wallet! I can't express this enough. You should use a strong password longer than 15 characters. This password should contain numbers, symbols, and some capitalization! There is no need to have your wallet open 24 hours a day. Open it only when you need it. See - 'Getting Started' on the side bar.
This entire post has been written to be as close to ELI5 (Explain it like I'm 5) as possible - By request! If anyone wants to add/fix/correct anything in this message, please send a message to the mods <<-- Click blue text.
All blue text in this post can be clicked on. The blue text is a link to a picture, site or download file.
A very important message/reminder below.
25 Jan 1.5 pre-releases have started.
OLD VERSIONS The 1.4 update for the dogecoin wallet has been released. This update addresses the block chain error that occurred. This update is mandatory meaning you have to do this update. Also further down the page you can read up about the block chain. You MUST make sure you're on the correct block chain and the old block chain has been removed.
For a Windows computer the version must be 1.4. - 1.4.1 just released! See below
For a Apple Mac Computer the version must be 1.4
Download links:
[Windows Download Link]( <<--Click to start download
Windows Download Link 1.4.1 UPDATED 19JAN
Mac Download Link <<--Click to start download
Mac users can join this thread if there are any problems
Android (phone): Please see This post
To update, simply download the new version from the download link above. Open the downloaded file and extract the contents of the downloaded file into any new folder or location on your computer. If you put the files into a folder you can name the folder anything you want but make sure you remember that this is the latest version of the software.
You don't have to remove your folder containing the old version of the wallet. You can place it in a folder called 'Old versions of dogecoin wallet' if you like.
Now you can click on the Dogecoin icon contained in the new folder to open your version 1.4 wallet.
What happens if I get an error when I open the new wallet?
An error was reported called "11DbException"
If this happens Download this file and place it in the same folder as your updated wallet. Open the file you just downloaded called "Dogecoin OPEN' and wait. This might take 2 or 3 minutes.
Also jtlarousse has found a solution that worked on Windows. Please follow carefully and make backups before starting.
Reebzy might have found a solution for Apple Mac
Blockchain fork 101: The block chain is a ledger or document created containing every transaction that has ever happened. This file can be quite large. Bitcoins ledger is over 15GB. At some point this document/ledger split into two separate documents known as a fork.
How do I know if I am on the right block chain?
Go to your newly updated dogecoin wallet and open it. Click on Help>>Debug next Observe the current block number
*Note the example numbers in the pictures might be out of date by the time you read them
Now go over to . This website is the official Dogecoin blockchain website. Check the block number they're reporting
The number you found in your wallet and the number reported on the website should close. There might be a difference of 100 blocks depending on when you last refreshed your wallet or how long it took for you to get from one step to the next step in this guide and if the dogechain website is lagging.
My numbers are very different. How do I get back onto the right block chain?
For windows:
1)Close down the Dogecoin wallet client.
2)Go to your data folder: C:\Users[your windows log-in name]\AppData\Roaming\DogeCoin
3)Delete the Dogecoin.conf file. Do not delete the wallet.dat file!
4)Download this update file and place it into the Dogecoin folder where the other file was deleted.
For Apple Mac:
1)Close down the Dogecoin wallet client.
2)Go to your data folder: ~/Libarary/Application Support/Dogecoin
3)Delete the Dogecoin.conf file. Do not delete the wallet.dat file!
4)Download this update file and place it into the Dogecoin folder where the other file was deleted.
Next visit this post by Netcodepool for instructions on how to manually download the correct block chain and install it.
Much Thanks. 
Edit: Some posts were removed from this thread. To limit confusion.
Check this post for details about mining pools that were/are using the wrong fork.
Did you send coins only to find out you're on the wrong chain? See this post to get them back
An Apple Mac support thread has been made by voidref (The mac developer). If you're having troubles please see this thread
Some shibes have reported their wallets wont sync. Please check to make sure your firewall, antivirus, malware scanner or similar programs are not blocking it the wallet. You can add rules to these programs to allow the wallet to make contact with the internet. It's not advised but possible to also disable the software for a short amount of time. Don't forget to enable the software again afterwards.
Is your wallet crashing? Try this helpful tip from gandhikahn or if you're using windows try the 1.4.1 update above.
submitted by 42points to dogecoin [link] [comments]

Dogecoin on Linux - The Complete Beginner's Guide

I'm writing this because I couldn't find a single condensed guide on compiling the wallet and running mining software on linux, specficially Ubuntu/Linux Mint. I combed Bitcoin and Litecoin forums for similar problems I was running into and eventually got everything nailed down, so here it is in one place, for new Shibes.
If you want to make a Dogecoin directory in your downloads folder to keep things organized, you will need to modify these commands to refelct the change. So instead of going to ~/Downloads/ you will need to go to ~/Downloads/Dogecoin and be sure to put the zipped files there when you download them, but the commands will be the same otherwise.
cwayne18 put in the work to make a PPA for the QT client here.
Ubunutu/Mint/Debian users should be able to install the client with the following commands:
sudo add-apt-repository ppa:cwayne18/doge sudo apt-get update && sudo apt-get install dogecoin-qt 
To update using this method, run
sudo apt-get update && sudo apt-get upgrade dogecoin-qt 
Compiling the Wallet Manually
I suggest using the PPA above, but if you want to compile manually, here you go.
1)Download the newest source from here. If you want to check out the Github page, click here
2)Unzip the package with the native client OR, navigate to your downloads and unzip
cd ~/Downloads unzip 
3)Now it's time to compile. You will need to install the dependencies, just copy and paste the following code. It will be a fairly large download and could take some time. It is always important to update before installing any new software, so we'll do that first and then install the dependencies.
sudo apt-get update sudo apt-get upgrade sudo apt-get install libssl-dev libdb-dev libdb++-dev libqrencode-dev qt4-qmake libqtgui4 libqt4-dev sudo apt-get install libminiupnpc-dev libminiupnpc8 libboost-all-dev build-essential git libboost1.53-all-dev 
4)Once that is done, go to the doge-coin master directory and compile:
cd ~/Downloads/dogecoin-maste sed -i 's/-mgw46-mt-sd-1_53//g' qmake USE_UPNP=- USE_QRCODE=0 USE_IPV6=0 make -j3 
After running the qmake command you will likely see some text similar to
Project MESSAGE: Building without UPNP support Project MESSAGE: Building with UPNP supportRemoved plural forms as the target language has less forms. If this sounds wrong, possibly the target language is not set or recognized. 
It's perfectly normal, so don't worry about that.
Your Dogewallet is ready to go! The executable is in ~/Downloads/dogecoin-maste and called dogecoin-qt. Your wallet information is in ~/.dogecoin. You can run the wallet at any time by opening terminal and typing
cd ~/Downloads/dogecoin-maste ./dogecoin-qt 
Future upgrades to dogewallet are easy. Back up your wallet.dat, and simply follow the same directions above, but you'll be unzipping and building the newer version. You will likely need to rename the old dogecoin-master directory in ~/Downloads before unzipping the newest version and building. Also, it is likely that you will not need to install the dependencies again.
Alternate Method For Installing Dogecoin Wallet from Nicebreakfast
After installing the dependencies listed in step 3, open terminal, then navigate to where you want Dogecoin Wallet stored and run:
git clone ./ ./configure make 
then when the wallet is updated just run
git pull 
from the dogecoin directory.
GPU Mining
GPU mining requires CGminer. My suggestion is to get the executable already built. The creator of cgminer has removed the built file from his website, but I've uploaded it here
sudo apt-get install pkg-config opencl-dev libcurl4-openssl-dev autoconf libtool automake m4 ncurses-dev cd ~/Downloads tar -xvf cgminer-3.7.2-x86_64-built.tar.bz2 
Don't use anything newer than 3.7.2. The newer versions of CGMiner don't support GPU mining.
That's it! You have cgminer ready to go! You will run cgminer with the following syntax
cd ~/Downloads/cgminer-3.7.2-x86_64-built/ ./cgminer --scrypt -o stratum+tcp://SERVERNAME:PORT -u WORKER.ID -p PASS 
A good guide for fine tuning cgminer can be found here; follow the litecoin example.
I had trouble getting cgminer running with a single line command, but running it via an executable .sh file works. This is covered in the cgminer setup guide I posted above but I'll put it here too. In the same directory that has the cgminer executable, you need to make a file called and make it executable. It should contain the follwing:
export GPU_USE_SYNC_OBJECTS=1 export GPU_MAX_ALLOC_PERCENT=100 export DISPLAY=:0 find *.bin -delete sleep 5 ./cgminer 
Then you can call cgminer in terminal by doing ./ You will need a cgminer.conf file containing all your options. All of this is covered in the guide that is linked above.
A quick note about AMD drivers: They used to be a huge PITA to install and get working, but the newest Catalyst drivers are great. There's a GUI installer, everything works out of the box, and there is a lot of documentation. You can download them here: AMD Catalyst 14.6 Beta Linux
CPU Mining
For CPU mining I use minerd because it doesn't require any work to get running, simply download it and get to work. Download the built file for your machine 32-bit or 64-bit, and then unzip it and you're ready to go!
cd ~/Downloads tar -xvf pooler-cpuminer-2.3.2-linux-x86.tar.gz 
The executable is called minerd and it will be in ~/Downloads but you can move it to wherever you like. To run it, pull up terminal and do
cd ~/Downloads minerd --url=stratum+tcp://SERVER:PORT --userpass=USERNAME.WORKERNAME:WORKERPASSWORD 
You're done! Happy mining!
Common Issues
I ran into this and I've seen others with this problem as well. Everything installs fine but there is a shared library file that isn't where it should be. In fact, it isn't there at all. cannot open shared object file: No such file or directory 
In terminal, do
sudo updatedb locate 
And it will probably return a path /lib/x86_64-linux-gnu. Inside that directory there's a library file called You'll need to make a symlink (aka shortcut) that links to So, assuming you're working with do this
cd /lib/x86_64-linux-gnu sudo ln -s 
Now if you do
ln -l 
You should see -> ./ 
Meaning you've made the symlink. Also, the text for will be blue.
submitted by Boozybrain to dogecoin [link] [comments]

[ELI5] How to send coins using

How to send coins from ANY wallet using


Because cold wallets, such as those stored offline in a text file as I keep recommending in my standard advice below:
All you need is a text file to put your wallets in, like this example from
1,"D7WBUpdgLRtG6WyPsqjhaKiJR65X8ZGnkZ","6KieLMW1poAzNVnmLuQZqA262gxEQ51eLGdDK8e2GL2B4LHCKKb" 2,"DM8LT16d49zHr8ByXbUwZb9UBXDGMaZRdc","6Ktgxdv6vN9v2bDHwcJBBb3oMRAgXJumESzBnxaXUSGFZoq6pWQ" 3,"D5UCa51AfxjtVHQ46oYXe2YfkctTeLXPhx","6L2WSPWadRYCwt2L1CxH6zC7PoTYY3KyjxdiUoCqi5eyq6hQKvj"
Use to move coins. Download both sites and run them offline. Use to check balances and transactions. See for tutorial. And read the ELI5s (and my history) for more info.
Are without doubt THE SAFEST way to store your coins. Plus, they consume no resources. No bandwidth, no network stress for every node we have, no storage of 20Gb+ blockchains, no weeks of waiting for things to sync, no tearing your hair out and posting desperate pleas for help, and most importantly, no coins irretrievably lost because you or your client screwed up.


Wallets, ALL WALLETS are nothing but numbers. Very large numbers, but fundamentally no different from “7”, “42”, “911” or a phone number. They cannot be created nor destroyed, and you either know them or you don’t. Anyone who knows a key can use it to spend any coins it controls. Anyone who doesn’t know it, can’t. Don’t be the guy who doesn’t know his own keys. Keep them safe. Make copies. Keep those safe. Don’t let your friends, kid brother or random burglar find them, but don’t lose them either.
The only other thing you need for a fully functional wallet is a way to spend coins. is such a way. There are others, such as which tomcarbon built.
Oh, and you can and should download it and run it locally.


The default entry point for is because this settings page is very well hidden. Its in the tiny gear wheel on the Broadcast page.
Looking across the top of the page, you can see
  • + New
  • Verify
  • Sign
  • Broadcast
  • Wallet
  • About
We’re only going to use three of these. New, Sign, Broadcast.
Now, keep in mind that is an old Bitcoin tool which tomcarbon added Dogecoin to. Sometimes it thinks its dealing with Bitcoin still, so if you see anything odd, go and make sure you’ve selected Dogecoin in the Settings page.


This tool should be the only place you spend coins. Sure, some clients may look more convenient, but they all suffer from a very big coin-losing flaw. Whenever you split a UTXO, they create a new wallet to send the change to. And they DON’T TELL YOU! This means unless you back up after every transaction, you run a high risk of finding all your coins have ‘disappeared’ from your wallet, and you don’t recognise where they went.
So if you use a client for the convenience as well as a text list of your wallets, you won’t know to add a new wallet to your masterfile. Its best to ditch the clients entirely.


Now we come to the nitty-gritty. Lets use those three wallets above and assume that #1 is the source, #2 the destination and #3 the change wallet. Note that these won’t actually work, as none of them have ever been used, but they will do as examples.
New Transaction
Located at the bottom of the New menu, this will give you a page to enter your wallets and amounts.
In the top field, you enter your source address or Key. If you use the key, it will calculate the address when you click the Load button, which should match what you expected. Note that Load only brings in the first 100 UTXOs. This is so that you can retrieve coins from high-volume wallets which would kill any client. is in fact the ONLY WAY to do this, as even QT falls over around 600 UTXOs.
You will see the total balance that was loaded in the Transaction Fee field. And also in the Inputs tab, where you can go to adjust which UTXOs to spend.
Now you need to add the wallet(s) and amounts to send to them. Lets suppose the source contained a single UTXO for 1,000 Doge. You want to send 500 of them. So you would enter the #2 address in the Address field, and 500 in the Amount field. The Fee now changes to 500, which is not what you want.
So you click the + button to bring up a new line, enter the change address and the other 500, making the fee zero.
And you’re done. Check that the Fee is indeed zero. Check that the amounts shown in the Outputs and Inputs tabs match exactly.


There is a bug which will send all the coins to the miners if the Outputs exceed the Inputs. I would have expected the Fee to show as negative in such a situation, but it doesn’t. BE WARNED!
Once everything looks right, hit the Submit button.
This will give you a block of hex code. Copy it.
Go to the Sign tab and paste it. Add your private key for the source wallet and click Submit. Note this can be done offline for safety.
This will give you another block of hex, the SIGNED transaction.
Copy this and paste it in the Broadcast tab and click Submit.
That’s it. Your coins are on their way. Make a cuppa and settle in while they arrive in a minute or three.
Note: All fields retain their values unless you refresh the page! This can be a boon when doing multiple transactions, such as when emptying a huge wallet. But it can also be a trap for the unsuspecting. Refresh or close the window when you’re done.


Who should use this?
Absolutely EVERYONE!
Even if you’re wedded to your client in some satanic blood-contract, you should still know how this works, because sooner or later you’re going to have a problem you can’t fix without it.
Definitely download the site and store it on every device you have. On every USB backup of your wallets. On your phone (well, except iOS which doesn’t do local HTML), etc, etc, etc.
Oh, and if you’re a programmer SmartyShibe, do consider improving the code over on GitHub.
EDIT: added courtesy of AtomHearth
submitted by Fulvio55 to dogecoin [link] [comments]

Much concern: Dogecoin block chain HAS SPLIT

Hey shibes,

Much bad news. THE DOGECOIN BLOCK CHAIN HAS FORKED. This is a bad thing.

ELI5: Your client is constantly downloading blocks and processing them, which is the way that Dogecoin works. Ten days ago, the developers made a change to the Dogecoin client that raised the limit of coins in a block from 500 million to 10 billion. So now some folks are running Dogecoin clients without that change, because they are older, and some folks are running newer clients. In block 42279, a transaction that broke the rule -- containing more than 500 million DOGE -- has prevented these older clients from advancing on the correct chain and they are now working on a bad ledger.
If you are attempting to send transactions and you hit this behavior, you ARE adding transactions to the bad chain.
There is a current risk of double spending and a lot of people are working on a bad ledger, both with mining and their personal clients. STOP sending DOGE (including pool payouts) until this situation is resolved by people that know more than I do. It might appear that you are still advancing past the bad block but your client might be going down the wrong fork!
Details: My client is synced and fine, and I sent a transaction in the last few minutes, but I've heard from several friends that they are stuck on a prior block have forked off the main ledger after block 42279. Apparently, 10 days ago, there was a commit to the dogecoin client that raised the transaction limit from 500 million DOGE to 10 billion DOGE:
In block 42279 a 500m DOGE transaction was submitted which broke the block chain on clients older than that commit. I have heard from three separate folks now that their clients are stuck on block 42279 advancing on a separate Dogecoin chain.
We have a blockchain split on our hands. Bitcoin went through one of these too. It's going to need intervention.
What do I do? Stop sending DOGE and wait. I would also suggest waiting until the mining situation is sorted out, because there is a double-spend risk right now. You can view your client's current block in the Debug menu, under Help, for the Qt client.

UPDATE 4:48 AM UTC / 11:48 PM EST

How do I know if I'm on the wrong fork?

UPDATE 5:14 AM UTC / 12:14 AM EST

The network is responding. Between block 42475 and 42480 on the good chain, the network hash rate dropped from 20 GH/sec to 15 GH/sec and the difficulty dropped from 320.3 to 253.3.
Here's my getmininginfo from 2 minutes ago:
{ "blocks" : 42502, "currentblocksize" : 0, "currentblocktx" : 0, "difficulty" : 253.32507890, "errors" : "", "generate" : false, "genproclimit" : -1, "hashespersec" : 0, "networkhashps" : 14678218267, "pooledtx" : 698, "testnet" : false } 
That's what the good chain looks like.

UPDATE 5:32 AM UTC / 12:32 AM EST

My test client that I resynced as an experiment ended up on the bad fork. There's going to need to be an intervention here similar to Bitcoin's.

UPDATE 5:50 AM UTC / 12:50 AM EST


UPDATE 7:31 AM UTC / 2:31 AM EST

Okay, I'm done with this thread, folks. The Dogecoin developers are on it and the amount of abusive private messages that I'm receiving mean I'm washing my hands.
Look for an official thread from developers next, the information is out and my role is done.
Credit to hoopycat -- please tip him -- who discovered the source of the problem, I'm trying to get the word out right now. I do not get credit for this post.
submitted by lachryma to dogecoin [link] [comments]

[dev] Dogecoin 1.10 IS OUT NOW. This is not a drill. You can tell by the lack of drilling noises

Yes, finally, after months of development and beating on it with hammers, Dogecoin Core 1.10 is out now: - for Windows users you probably want to grab the setup-unsigned.exe versions (the .zip files are for anyone who just wants the binaries).
BACK UP YOUR WALLET BEFORE YOU UPGRADE. We've had zero problems with upgrades so far, but still, just to be safe.
You will have to reindex on first run of Dogecoin Core 1.10, which will take 2-3 hours. I suggest running it overnight. If you use the QT (graphical) client, it will prompt you to reindex. If you run the daemon, use the "-reindex" option when you launch to start the reindex process. Again, this only has to be done once while the index format is updated to add more sanity checks. Your wallet balance will reflect the blocks that have been reindexed, while the process runs, don't panic. Do not attempt to send coins while the reindex runs, however, or you may find you've sent invalid transactions.
This is a major update and a critical security update. If you use Dogecoin Core, you MUST update to 1.10 to remain secure. If you for whatever reason absolutely cannot update (i.e. cannot take a service down to reindex) you can use Dogecoin Core 1.8.3, which contains the most critical fixes: . Even then, we highly recommend updating later if at all possible.
This release includes all of the changes in Bitcoin Core 0.9 and 0.10, including a huge speed boost to download/sync, a broad range of security fixes, and the framework for future improvements such as blockchain trimming and smart contracts (yes, you read that right, smart contracts).
If you're an individual user please update NOW. If you're a merchant, exchange, payment processor or service provider, please test and update as soon as possible. If you're a miner, please update after the 17th so we have time for the new client to be deployed. This update introduces version 3 blocks (BIP 66 for those who know what that is), which are part of the security fixes, and the more clients update before they're mined, the easier the rollout will be.
To re-iterate - seriously, you need to update. This client has been in testing for literal months, it's stable, there isn't another update just around the corner, get this one.
Lastly, for anyone who wants to run a Dogeparty wallet server (mostly this means coinwarp), there's a modified version of 1.10 with extensions to support Dogeparty wallets. Unless you need this version (i.e. someone tells you you need it), just get 1.10 from above instead. If you do need it, it's at
submitted by rnicoll to dogecoin [link] [comments]

Ravencoin Open Developer Meeting - 2/15/2019

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:02 PM
Hello everybody!

theking - Last Friday at 2:02 PM

Seems likes it’s been so long since this meeting was held. At least a month 📷

Tron - Last Friday at 2:02 PM

Hi all!!!

Tom - Last Friday at 2:02 PM

Big boss is here !(edited)

BigZim - Last Friday at 2:03 PM

Oh hi

theking - Last Friday at 2:04 PM

Hi @Tron

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:04 PM

Topics for today: Release 2.2.2, Mobile Wallet, Restricted Assets, SLC Raven Meetup📷1

truedev - Last Friday at 2:05 PM


RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:05 PM

Release 2.2.2 GO

J. | - Last Friday at 2:05 PM


RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:05 PM

BTW, blondfrogs won't be able to join us today. 📷

corby - Last Friday at 2:05 PM

Hi all

Chatturga - Last Friday at 2:05 PM

Blondefrogs has been working on the 2.2.2 update. He isnt here today, but he left this tidbit for the meeting:(edited)"Release 2.2.2 has a bunch of new updates. The sync speed fix that was released in 2.2.1 has been updated even more to use less memory/ram and uses less CPU. Each node used to hold all addresses that contained an asset as well as the amount in those addresses. That is now optional with the -assetindex flag. Which can be put into the raven.conf or added as a parameter when starting the wallet. Some other wallet issues were also fixed with this memory update. This is considered an mandatory update, especially if you haven't updated to 2.2.1 which resolved a potential fork bug fix. I would still suggest updating to 2.2.2 even if you are on 2.2.1."📷6

Jeroz - Last Friday at 2:07 PM

wen source?📷1

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:07 PM

There's a PR that was just moved to Develop.When is now

Jeroz - Last Friday at 2:08 PM

great 📷

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:08 PM

It'll be merged by the devs to master and then binaries should be posted soon

truedev - Last Friday at 2:09 PM

any idea when dividends will be functional?

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:09 PM

A bunch of testing has been happening and is currently running on the seed-nodes.

Tron - Last Friday at 2:10 PM

No timeline for dividends, but it is the one function that doesn't need any changes to consensus. And it can be done on tier 2 with a python script. The plan is still to build in a rpc call.📷2

truedev - Last Friday at 2:11 PM


SpyderDev - Last Friday at 2:12 PM

We have been focusing on sync performance and have been running many tests. I've added an image of the results of this testing. Currently we still want to work on getting the Windows QT sync times faster (at least closer to what they are using just ravend). Overall we are very happy with the speeds and hope it will help people that have struggled getting their nodes up to date.(edited)📷

Jeroz - Last Friday at 2:13 PM

Yeah that table completely puzzled me

[Master] Roshii - Last Friday at 2:13 PM


Jeroz - Last Friday at 2:13 PM

Fast branch is 2.2.1? or 2.2.2? Develop branch is 2.2.0?

SpyderDev - Last Friday at 2:15 PM

Sorry, should have clarified that. I was testing while it was still under development. On the table the top is the new-sync code, the bottom is the old "assets" release. As of about 5 minutes ago all of this code is on the develop branch.

Jeroz - Last Friday at 2:15 PM

Although syncing is mostly bottlenecked by cpu speed, that 16 core windows-qt still looks off to me. I synced windows Qt using 2.2.2 in ~2h on a i5-7600K.ok

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:17 PM

Okay, we good to move to the Mobile update?

SpyderDev - Last Friday at 2:17 PM

The Windows box is an AWS instance and there is some concern that the remote desktop could be slowing the QT UI down causing the horrible sync times. I am working on getting a local Windows 10 resource and will have updated information once that is ready (early next week).

Jeroz - Last Friday at 2:18 PM

ah that might explain. Ubuntu qt was 45 mins for me

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:18 PM

CoolOkay, Mobile!Go!

[Master] Roshii - Last Friday at 2:18 PM


RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:19 PM

@[Master] Roshii has been working closely with some of the other devs to get the iOS version out the door.Android will follow closely.

Jeroz - Last Friday at 2:20 PM

is android an easy port?

J. | - Last Friday at 2:20 PM

Usually its the case(?), i mean easier 📷(edited)

SpyderDev - Last Friday at 2:20 PM

Just copy and paste right Roshii 📷

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:20 PM

LOLNo, usually its a completely new development effort.For the RVN Wallets they are both written in native iOS/Android code.

[Master] Roshii - Last Friday at 2:21 PM

So the iOS and Android use the same Core SPV module written in C, and it's the most difficult part.I have already did some work when it comes to Android, and it's 70% finishedHave also to port all the changes we lately did to the iOS wallet ...

boatsandhoes - Last Friday at 2:21 PM

yeah, unfortunately its not as easy as cut and paste for ios to android

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:21 PM

Anybody interested in installing the TestFlight version and helping us test?

boatsandhoes - Last Friday at 2:22 PM


J. | - Last Friday at 2:22 PM

For android? sure.

BW__ - Last Friday at 2:22 PM

Android? yes.(edited)

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:22 PM

I'll talk to Apple about adding Android support to TestFlight.Might be a while.

J. | - Last Friday at 2:22 PM


RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:22 PM

Anybody on here using iOS?

Jeroz - Last Friday at 2:22 PM

Yeh me

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:22 PM

besides me...

[Master] Roshii - Last Friday at 2:23 PM

Android is very close, fortunately I'll have enough coffee in Morocco to finish the wallet in two weeks.(edited)📷4📷5

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:23 PM (400 installs available)Join the RVN Wallet betaAvailable on iOS📷

theking - Last Friday at 2:23 PM

I will test iOS if needed

[Master] Roshii - Last Friday at 2:23 PM


RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:24 PM

Some of the devs have been doing a bunch of testing on iOS but we would love others to help.Bugs can be reported on GitHub to RavenProject/ravenwallet-ios development by creating an account on GitHub.📷

truedev - Last Friday at 2:25 PM

how confident are you that apple will allow it on the appstore

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:25 PM

It's already in the App store.

truedev - Last Friday at 2:25 PM


RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:25 PM

That wasn't easy though.

truedev - Last Friday at 2:26 PM

yah figured, a lot of coins have been completely rejected(edited)

Chatturga - Last Friday at 2:26 PM

The devs already jumped through Apples 152,315 flaming hoops to get it in there.

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:26 PM

Yup, many meetings and phone calls.

J. | - Last Friday at 2:26 PM

wen rvn modular phone

Jeroz - Last Friday at 2:27 PM

Looking good📷📷7

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:28 PM

Okay, any questions about iOS release?

jaysonb - Last Friday at 2:28 PM

seed word format changed? i seem to have to have same words. did i need to delete and install fresh?

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:29 PM

No, it used your old ones.Always have your 12 words. especially when testing.

ravencoin maximalist 🧘🏻♂ - Last Friday at 2:30 PM

I’ve got iOS

Tron - Last Friday at 2:30 PM

If you use your 12-words, and then sync, and you're missing funds. Go here: — Testing iOS Wallet – Tron Black – MediumThank you for helping us test the Ravencoin iOS mobile wallet. Since you are in an early group of testers, you might have used the…

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:30 PM

Sweet, install and report bugs.

Tron - Last Friday at 2:30 PM

Or just go there...

jaysonb - Last Friday at 2:30 PM

that article scared me so i moved everything off.but i'll put some back on now

ravencoin maximalist 🧘🏻♂ - Last Friday at 2:31 PM


RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:31 PM

That's unfortunate. You don't need to be scared ever if you have your 12 words.

[Master] Roshii - Last Friday at 2:31 PM

android current state(edited)📷

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:32 PM

Here's the install link one more time for those that have joined late: the RVN Wallet betaAvailable on iOS📷Okay, Tron's topic: Restricted Tokens

Tron - Last Friday at 2:33 PM

I have an idea.(edited)📷7📷6

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:34 PM

That several other devs have helped with. 📷

Tron - Last Friday at 2:34 PM


SpyderDev - Last Friday at 2:34 PM

and lawyers

Tron - Last Friday at 2:34 PM

When the project started, ICOs were the big thing. Now it is STOsThe main difference is the legal wrapping and rules around securities.If Ravencoin has two more token types (Tags and Restricted Assets), there are lots of ways to make compliant tokens.Importantly, it doesn't affect the existing tokens at all.Tags - Tokens that can be sent only by the issuer once (with metadata).These tokens start with (hashtag)(edited)📷8

SpyderDev - Last Friday at 2:37 PM


Tron - Last Friday at 2:37 PM

The Restricted Assets start with $, and can be frozen by the issuer. But they only move between tagged addresses.(edited)

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:38 PM

Tags can be sent to a user's address after the issuer has done the necessary due diligence for an STO issuance.(edited)

Tron - Last Friday at 2:38 PM

The issuer determines which tags the Restricted Asset will honor.This can be used for lots of different use cases.

EEE - Last Friday at 2:38 PM

Stunning interface guys

boatsandhoes - Last Friday at 2:39 PM

will that determination be a setting in the wallet?

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:39 PM

Restricted assets can then only be sent to addresses that are allowed and have the proper Tags.

boatsandhoes - Last Friday at 2:39 PM


J. | - Last Friday at 2:39 PM

Did you guys get contacted by some entity* whos forcing the restricted address policy? or is this done as precautionary measure? At first glance your idea sounds good Tron.(edited)

Tron - Last Friday at 2:39 PM

Example: $UBER token only moves among addresses tagged with #KYC

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:40 PM

So Ravenland will have to buy a bunch more spam tokens.📷4

SpyderDev - Last Friday at 2:40 PM


boatsandhoes - Last Friday at 2:40 PM

so is the $ something that can be added to an existing asset?

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:40 PM

It's not a forced thing. But adding the ability for Raven to be used in new use cases where legal requirements exist.

Tron - Last Friday at 2:40 PM

Not contacted by anyone, and not precautionary. Ravencoin Assets are just tools. This is just another tool that will help issuers of security tokens.📷9📷4

BW__ - Last Friday at 2:41 PM

Love it.

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:41 PM

It'll be a new token type that you can create @boatsandhoes📷1

ravencoin maximalist 🧘🏻♂ - Last Friday at 2:41 PM

That sounds awesome

SpyderDev - Last Friday at 2:41 PM

I for one am very excited about this...📷4

Hans_Schmidt - Last Friday at 2:41 PM

How does the $ token owner specify the required # tags?

DeejayQQ - Last Friday at 2:41 PM

Can the same name have different token type?Sorry need time to digest

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:42 PM

Still working out the details. Tron will be posting additional info about the idea soon.

Steelers - Last Friday at 2:42 PM


RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:42 PM

Feedback is wanted!

Tron - Last Friday at 2:42 PM

Q: Was this originally the plan for Ravencoin? A: No. This is in response to the regulatory ramp up in 2018 in some jurisdictions which requires that only known individuals or entities to operate peer-to-peer on certain tokens. For jurisdictions that allow unrestricted peer-to-peer transfer, we strongly encourage use of the original Ravencoin assets. The Restricted Assets are an adaptation to satisfy burdensome, privacy-destroying regulations, with a goal of reducing information replication which makes Ravencoin Restricted Assets a better alternative to those being promoted now.

jaysonb - Last Friday at 2:43 PM

all nodes will validate the transactions not just those interested in the transaction - i assume all will validate..

boatsandhoes - Last Friday at 2:43 PM

so essentially any name already secured in the hopes of having that functionality are worth less because they wont be able to?

theking - Last Friday at 2:44 PM

Can the restricted assets be time based in any way? For instance, in some STO regulated environment, there is a lockup for some period of time after issuance, but then after a certain period of time the restriction goes away and the securities can be traded. Is that contemplated at all?

DeejayQQ - Last Friday at 2:44 PM

If I already have Tron as my asset, there could be another Tron but under a different token type such as restricted assets?

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:44 PM

Yes all nodes will do consensus checks.

corby - Last Friday at 2:44 PM

@boatsandhoes there's going to be a grace period where you can purchase $XXX if you own XXXon the order of months

boatsandhoes - Last Friday at 2:45 PM

📷 📷 📷 📷

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:45 PM

Yes, you have the TRON asset and you can also have the $TRON asset.(edited)

Tron - Last Friday at 2:45 PM

Regarding the lockup....

boatsandhoes - Last Friday at 2:45 PM

how many RVN for that?

Tron - Last Friday at 2:45 PM

Rule 144 under the Securities Act of 1933 This is an important rule to be aware of in terms of privately held securities. This rule provides the most commonly used exemption for holders to sell restricted securities (Note: For context, a restricted security is a security sold in an exempt offering, except for Reg A+). The general idea is that you can publicly resell your “restricted” (privately sold) securities only when the restricted legend is removed. The solution Ravencoin Restricted Assets provides is the ability for the Iissuer to Freeze the asset ininto the holders account. The qty will be visible, and the frozen status will be visible. The meta-data for a Freeze can specify 144_Restricted. The issuer can Unfreeze to release the 144 restriction.Similar for Reg D 1-year lockup.@theking

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:46 PM

@theking ^^

DeejayQQ - Last Friday at 2:46 PM

What is the timeline for this restricted asset to be implemented?📷1

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:46 PM

No timelines yetStill in the ideation phase.

SpyderDev - Last Friday at 2:46 PM

Fresh off the press...

DeejayQQ - Last Friday at 2:46 PM

Ok, idea for nowGot it

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:46 PM

Wanting input for the idea.

boatsandhoes - Last Friday at 2:47 PM

a preset for lock up settings would be nice

Jeroz - Last Friday at 2:47 PM

What about the ability to move an asset from restricted to unrestricted after grace period similar to the reissue ability? By the issuer(edited)

boatsandhoes - Last Friday at 2:47 PM

adjustable preset*

DeejayQQ - Last Friday at 2:48 PM

If this restricted assets would help underlying token listed on exchanges for trading by satisfying the legal requirements, I don’t see why not. There are only benefits📷2

boatsandhoes - Last Friday at 2:48 PM

yeah, win win

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:48 PM

There is something similar in vote tokens.

corby - Last Friday at 2:48 PM

@Jeroz the issuer would be able to "reissue" and relax restrictions

DeejayQQ - Last Friday at 2:48 PM

Just throwing things out here. Can we just make all existing tokens crested so far restricted assets?*created

boatsandhoes - Last Friday at 2:49 PM

stupid question, is it possible to have burned rvn cost for the $ to add onto the block reward as a bonus?(edited)

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:49 PM

No, @DeejayQQ there should be both usecases available in the platform.

corby - Last Friday at 2:49 PM

We (my dog and I) are envisioning a differentiated space where we can charge a lot more RVN to keep non-serious people out..(edited)

Tron - Last Friday at 2:49 PM

@Jeroz Yes, as long as the asset is still "reissuable", you could change the logic from (#KYC & #ACCREDITED) to just #KYC📷3

Jeroz - Last Friday at 2:49 PM

I'm just worrying about the name uniqueness if you can have #BANANA and $BANANA

BW__ - Last Friday at 2:50 PM

Is it fair to assume that tags can be standardized for specific purposes? If so, should we create something akin to an 'ERC' in git repo?

Jeroz - Last Friday at 2:50 PM

@Tron sounds cool

truedev - Last Friday at 2:50 PM

honestly, I think you should be able to buy/create an asset in a set, with all types(edited)

boatsandhoes - Last Friday at 2:50 PM

^that part

Hans_Schmidt - Last Friday at 2:51 PM

Since the #KYC tag is just locked to an address, what prevents someone from selling their address and thereby the KYC?

corby - Last Friday at 2:51 PM

The "#" types won't trade -- they're just stamps to stamp addresses as qualified-to-hold-some-stuff..

Tron - Last Friday at 2:51 PM

The tags are created by the users. The system is still jurisidiction agnostic.

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:51 PM

@Hans_Schmidt nothing really, the same thing as selling your username password to any other existing financial app account.

corby - Last Friday at 2:51 PM

@Hans_Schmidt Real world networks, high cost of entry (for serious applications)For non-serious applications, nothing

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:51 PM

You still have the liability associated with that account though.

Jeroz - Last Friday at 2:52 PM

@corby what about BANANA/ vs $BANANA/ ?Or do you want to make them subassets?

boatsandhoes - Last Friday at 2:52 PM

@Jeroz better safe than sorry, just swoop both

Tron - Last Friday at 2:52 PM

A country could require that #SOMECOUNTRY tag has to exist before moving $SPECIALASSET to an address. The users set the rules. #KYC was just an example because it is an industry problem at the moment.

corby - Last Friday at 2:52 PM

#BANANA, $BANANA, TRICYCLE, and BANANA can all coexist just fine I think..

theking - Last Friday at 2:53 PM

Thanks @Tron. This is great and I think something that will enable raven to become an even more widely used platform.📷4

Tron - Last Friday at 2:53 PM

That's the hope. I think it solves some real problems that the industry is trying to solve through incompatible ERC-20 experiments.📷3

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:54 PM


boatsandhoes - Last Friday at 2:54 PM

what is the purposed cost for $ in addition to an existing asset?

corby - Last Friday at 2:54 PM

People that own #THESE I am calling "Qualifiers" -- they just stamp their mark on addresses. Issuers of $THESE need to establish trust with #THESE and #THOSE and then decide what restrictions to apply.📷1

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:54 PM

5 mins left. Stay on this topic or switch to meetup?

Tron - Last Friday at 2:55 PM

@boatsandhoes Not determined.

Jeroz - Last Friday at 2:55 PM

yeah the idea is a nice proof of ownership / membership

DeejayQQ - Last Friday at 2:55 PM


Chatturga - Last Friday at 2:55 PM

TL;DR - The SLC meetup is in 1 month. Go to to indicate if you plan on attending so that we have a somewhat accurate headcount.MeetupSalt Lake City Ravencoin (Salt Lake City, UT)Ravencoin is a blockchain and platform optimized for transferring assets, such as tokens, from one holder to another, and is built on a fork of the Bitcoin code. It is intended to prioritize security,📷

corby - Last Friday at 2:55 PM

@boatsandhoes One Million Raven

Chatturga - Last Friday at 2:55 PM

Punch and pie

J. | - Last Friday at 2:56 PM

Can the SLC meetup made interactive for people that cant make it there?

theking - Last Friday at 2:56 PM

What about having just one name ( you first buy the standard raven token under whatever name you like) and then the holder of the owner token is the only one to create restricted tokens ? Might be some way to ensure no name confusion.📷4

boatsandhoes - Last Friday at 2:56 PM

what about that block reward bonus concept for purchasing $. would that work?

Chatturga - Last Friday at 2:56 PM

I dont know that we have the ability to make it interactive as far as Q&A goes, but I'll look into it. We should have it live streaming. @J. |📷2

BW__ - Last Friday at 2:56 PM

@Tron Is there same kind of logic layer to restricted assets?(edited)

Tron - Last Friday at 2:57 PM

@theking I like that idea.

Jeroz - Last Friday at 2:57 PM

Quick question that is offtopic but I think deserves an answer because it was asked a couple of times earlier this week: Will unique assets get a reissuable function? To change IPFS.(edited)📷2

Tron - Last Friday at 2:57 PM

@BW__ Yes. Simple and, or, not and parenthesis - limited in length.(edited)

boatsandhoes - Last Friday at 2:57 PM

@theking thats a good idea

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:58 PM

@Jeroz There is not a way to do that currently.

BW__ - Last Friday at 2:58 PM

@Tron That makes sense. Thank you.

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:58 PM

Just make sure your changes to the information have the same hash as the previous data and your golden. 📷📷1

Jeroz - Last Friday at 2:59 PM

Any plans on changing that, perhaps when introducing new types of assets?

boatsandhoes - Last Friday at 2:59 PM

i like that it cant be changed

corby - Last Friday at 3:00 PM

Thanks everyone!

theking - Last Friday at 3:00 PM

@Tron there was some info floating around about a 2nd later KYC solution ( from your recent podcast w Crypto Koala). Is that a separate solution someone is working on or part of this new concept?📷1

Tron - Last Friday at 3:01 PM

Starting with the introduction of messaging, every transaction can have an IPFS hash. Can be used as an public invoice, details about the transaction, etc.@theking The same new concept.

[Master] Roshii - Last Friday at 3:02 PM

Ok, we're done.

Steelers - Last Friday at 3:02 PM

How would Raven handle for instance a stock split?

BW__ - Last Friday at 3:02 PM

Are there sync concerns if a restricted asset logic layer is added?

Tron - Last Friday at 3:02 PM

@theking The KYC provider would store the KYC info, and send the Tag to an address with meta data that specifies that they're holding the KYC data. The KYC data would not be public, but could be audited.

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 3:02 PM

That way you could update information about the original unique asset with each transaction.@Steelers Just a simple re-issue of the asset

Tron - Last Friday at 3:03 PM

@bw_ The logic layer is only a small db that stores the meta-data about the Restricted Asset, and enforces the restriction in the consensus rules. Rule returns true/false.(edited)

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 3:03 PM

Thanks everybody! I have to run.

Jeroz - Last Friday at 3:04 PM

I'm looking forward to the discussions to let this take shape. Thanks all! 📷📷4

Tron - Last Friday at 3:05 PM

@BW__ It would work very similarly to the way the units works now. Each asset has number of units and any transaction that makes it too granular (more satoshis) will fail in consensus -- even if it gets past the RPC checks.Signing off. Thanks all!!!📷9📷4📷9
submitted by Chatturga to Ravencoin [link] [comments]

Ravencoin Open Developer Meeting - 1/4/2019

[14:04] Hi everyone! [14:04] :dabbitwave: [14:04] Hey Everybody! [14:04] Hello 😃 [14:04] Sorry we're getting started a bit late. [14:04] Topics: SLC Meetup (March 15th) [14:04] 👋 [14:04] Roadmap breakdown - posted to github [14:05] IPFS (integration) [14:05] greetings 👋 [14:05] So, SLC Meetup on the 15th! [14:05] Great! [14:05] Hi! [14:06] Hi all — a special thanks to the developers and congratulations on an amazing first year!!! # [14:06] <[Dev] Blondfrogs> Hello Everyone! [14:07] We have a tentative agenda with @Tron , @corby speaking. [14:08] We would like to have nice walkthrough of the Raven DevKit for the meetup. [14:08] We are planning on hosting a meetup in SLC at the Overstock building on March 15th from 6:00pm-9:00pm. It is free admission, but there is a page on where people can rsvp so that we have a somewhat accurate headcount for food. [14:08] sup guys [14:08] hey russ [14:09] We are planning on having a few speakers and have allotted a bit of time at the end for people to meet and greet each other. [14:09] can you guys link us to the page somewhere when thats available? 😄 [14:10] free food?! [14:10] todays topic? [14:10] yeah can we indicate pepperoni pizza [14:10] Sounds good to me @Jeroz Nothing ordered yet though. 😃 [14:10] only pepperoni pizza is served at true blockchain meetings right [14:10] :blobhide: [14:10] Absolutely. The itinerary just needs to be finalized and then I'll make a broad post about the rest of the details. [14:11] [14:11] 😭 so far away [14:11] West Coast! [14:11] @MTarget But there's pizza, so worth the travel time. [14:11] lol [14:12] I'll be watching the stream if its available since i'm from montreal/canada 😛 [14:12] Ah yes, I love $300 pizza 😉 [14:12] as long as I get to see your smiling faces @Tron @RavencoinDev then it's worth the time [14:12] We'll be there. [14:12] We'll be messaging additional details as they get finalized. [14:12] Greeting and salutations! [14:12] sup [14:13] Hey, $300 is considerably cheaper than 2 $3,700,000 pizzas. [14:14] Ok, switching topics... [14:14] yeah its a way to fly, [14:14] question is whether those piza's will be paid for in RVN coin or not :ThinkBlack: [14:14] Roadmap [14:14] It hasn't changed, just added some detail. [14:14] [14:15] nice [14:15] This now links to a breakdown for messaging, voting, anti-spam, and rewards (dividends) [14:15] will there be any additional RPC functionality coming in the future, thinking in terms of some functions that are only available in ravencore-lib [14:15] apologies if now is not time to ask questions, i can wait for later [14:15] "Phase 7 - Compatibility Mode" - that's new 😮 [14:15] The protocol for messaging is pretty well established, but the rest isn't in stone (code) yet. [14:16] can you give us details on compatibility mode? [14:16] In broad brush strokes. [14:17] The idea is to allow ravend to act as a daemon that looks like a single coin. [14:17] so ravend that only works with the bitcoin asset? [14:18] interesting [14:19] So you start it with an option to only work with a single asset/token account or something? [14:19] hmm compelling what is the reason for this? some kind of scale or performance? [14:19] ^ [14:19] Example: Configure ravend to listen for transfer RPC call for senttoaddress or sendfrom, but for a specific asset. This would allow easy integration into existing system for assets. [14:20] Only the daemon or the whole wallet UI? [14:20] yeah thats great, rpc functions dont allow us to do this yet, if i recall [14:20] or at least we depend more on ravencore lib [14:20] so like asset zmq [14:20] that's smart [14:20] @Tron it also sounds like it makes our life easier working with RPC, instead of core all the time for some functionality [14:21] if i understand correctly anyways [14:21] So you could run numerous instances of ravend each on their own network and RPC port, each configured for a different asset. You would need some balance of RVN in each one to cover transaction fees, then. [14:21] id be curious to know what all the advantages are of this [14:21] one more question, how would i decentralize the gateway between bitcoin mainnet/ravencoin mainnet? in the current RSK implementation they use a federated gateway, how would we avoid this? [14:21] it sounds neato [14:21] Just the daemon. The alternative is to get exchanges to adapt to our RPC calls for assets. It is easier if it just looks like Bitcoin, Litecoin or RVN to them, but it is really transferring FREE_HUGS [14:22] That makes sense. Should further increased exchange adoption for each asset. [14:22] hmm yeah its just easier for wallet integration because its basically the same as rvn and bitcoin but for a specific asset [14:22] so this is in specific mind of exchange listings for assets i guess [14:23] if i understand rightly [14:23] @traysi Gut feel is to allow ravend to handle a few different assets on different threads. [14:23] Are you going to call it kawmeleon mode? [14:23] Lol [14:23] I read that as kaw-melon mode. [14:24] same lol [14:24] so in one single swoop it possible to create a specific wallet and server daemon for specific assets. great. this makes it easier for exchanges, and has some added advantages with processing data too right? [14:24] Still keeping a RVN balance in the wallet, as well, Tron. How will that work is sendtoaddress sends the token instead of the RVN? A receive-RVN/send tokens-only wallet? [14:25] @traysi Yes [14:25] sendtoaddress on the other port (non RVN port) would send the asset. [14:25] This will be a hugely useful feature. [14:25] ^ [14:26] @Tron currently rpc function not support getaddresses senttowallet and this has to be done in ravencore lib, will this change you propose improve this situation [14:26] Config might look like {"port":2222, "asset":"FREE_HUGS", "rpcuser":"hugger", "rpcpass":"gi3afja33"} [14:26] how will this work cross-chain? [14:28] @push We'd have to go through the rpc calls and work out which ones are supported in compatibility mode. Obviously the mining ones don't apply. And some are generic like getinfo. [14:28] ok cool 👍 cheers [14:29] for now we continue using ravencore lib for our plans to keep track i just wondering if better way [14:29] as we had some issue after realising no rpc function for getting addresses of people who had sent rvn [14:29] @push | all of the node explorer and ravencore-lib functionality is based on RPC (including the addressindex-related calls). Nothing you can't do with RPC, although I'm not sure of the use cases you're referring to.. [14:29] interesting, so ravencore lib is using getrawtransaction somehow [14:29] i thought this may be the case [14:29] that is very useful thankyou for sharing this [14:30] look into addressindex flag and related RPC calls for functions that operate on addresses outside your wallet [14:30] thank you that is very useful, tbh i am not very skilled programmer so just decoding the hex at the raven-cli commandline was a challenge, i shall look more into this, valued information thanks as this was a big ? for us [14:31] Ok, things have gone quiet. New topic. [14:31] IPFS (integration) [14:31] GO [14:33] ... [14:33] <[Dev] Blondfrogs> So, we have been adding ipfs integration into the wallet for messaging. This will allow the wallets to do some pretty sweet stuff. For instance, you will be able to create your ipfs data file for issuing an asset. Push it to ipfs from the wallet, and add the hash right into the issuance data. This is going to allow for a much more seamless flow into the app. [14:34] <[Dev] Blondfrogs> This ofcourse, will also allow for users to create messages, and post them on ipfs and be able to easily and quickly format and send messages out on the network with ipfs data. [14:34] It will also allow optional meta-data with each transaction that goes in IPFS. [14:34] will i be able to view ipfs images natively in the wallet? [14:34] <[Dev] Blondfrogs> Images no [14:34] We discussed the option to disable all IPFS integration also. [14:35] @russ (kb: russkidooski) Probably not. There's some risk to being an image viewer for ANY data. [14:35] No option in wallet to opt into image viewing? [14:35] cool so drag and drop ipfs , if someone wanted to attach an object like an image or a file they could drag drop into ui and it create hash and attach string to transaction command parameters automatically [14:35] We could probably provide a link -- with a warning. [14:35] nomore going to [14:35] :ThinkBlack: [14:35] I understand that the wallet will rely on (phase 1). Is it not dangerous to rely on an external network? Or am I missing something? [14:36] hmm [14:36] interesting, i suppose you could hash at two different endpoints and compare them [14:36] if you were that worried [14:36] and only submit one to the chain [14:36] You will be able to configure a URL that will be used as an IPFS browser. [14:36] Oh ic [14:36] you wont flood ipfs because only one hash per unique file [14:36] <[Dev] Blondfrogs> There are multiple options for ipfs integration. We are building it so you can run your own ipfs node locally. [14:36] <[Dev] Blondfrogs> or, point it to whatever service you would like. e.g. cloudflare [14:36] this is very cool developments, great to see this [14:37] Just like the external block explorer link currently in preferences. [14:37] @[Dev] Blondfrogs what about a native ipfs swarm for ravencoin only? [14:37] We have discussed that as an option. [14:37] @push | Considering having a fallback of upload through and download through cloudflare. [14:37] <[Dev] Blondfrogs> @russ (kb: russkidooski) We talked about that, but no decisions have been made yet. [14:37] yeah, i would just use two endpoints and strcompare the hash [14:37] as long as they agree good [14:37] submit tran [14:38] else 'potentially mysterious activity' [14:38] ? [14:38] if you submitted the file to ipfs api endpoints [14:38] Will the metadata just be a form with text only fields? [14:39] and then you would get 2 hashes, from 2 independent services [14:39] that way you would not be relying on a central hash service [14:39] and have some means of checking if a returned hash value was intercepted or transformed [14:39] i was answering jeroz' question [14:40] about relying on a single api endpoint for upload ipfs object [14:40] We have also kicked around the idea of hosting our own JSON only IPFS upload/browse service. [14:41] I have a service like this that is simple using php [14:41] we only use it for images right now [14:41] but fairly easy to do [14:41] Yup [14:42] Further questions about IPFS? [14:43] contract handling? file attach handling? or just text fields to generate json? [14:44] trying to get an idea of what the wallet will offer for attaching data [14:44] Probably just text fields that meet the meta-data spec. [14:44] ok noted [14:44] What do you mean by contract handling @sull [14:45] We won't prevent other hashes from being added. [14:45] asset contract (pdf etc) hash etc [14:45] <[Dev] Blondfrogs> also, being able to load from a file [14:45] got it, thanks [14:47] Let's do some general Q&A [14:48] Maybe just a heads up or something to look for in the future but as of right now, it takes roughly 12 hours to sync up the Qt-wallet from scratch. Did a clean installation on my linux PC last night. [14:48] Any plans or discussions related to lack of privacy of asset transfers and the ability to front run when sending to an exchange? [14:48] ^ [14:48] Is there a way to apply to help moderate for example the Telegram / Discord, i spend alot of time on both places, sometimes i pm mods if needed. [14:49] Any developed plans for Asset TX fee adjustment? [14:49] also this^ [14:49] @mxL86 We just created a card on the public board to look into that. [14:49] General remark: = updated reflecting Tron's explanation. [14:49] @mxL86 That's a great question. We need to do some profiling and speed it up. I do know that the fix we added from Bitcoin (that saved our bacon) slowed things down. [14:50] Adding to @mxL86 the sync times substantially increased coinciding with the asset layer activation. Please run some internal benchmarks and see where the daemon is wasting all its cycles on each block. We should be able to handle dozens per second but it takes a couple seconds per block. [14:50] @BW__ no plans currently for zk proofs or anything if that's what you're asking [14:50] You are doing a great job. Is there a plan that all this things (IPFS) could be some day implemented in mobile wallet? Or just in QT? [14:50] i notice also that asset transactions had some effect on sync time as we were making a few. Some spikes i not analysed the io and cpu activity properly but will if there is interest [14:51] we are testing some stuff so run into things i am happy to share [14:51] @BW__ Might look at Grin and Beam to see if we can integrate Mimble Wimble -- down the road. [14:51] yeees [14:51] @J. | work with the telegram mods. Not something the developers handle. [14:51] i love you [14:51] @J. | That would be best brought up with the operators/mods of teh telegram channel. [14:51] @corby @Tron thnx [14:51] @S1LVA | we're planning on bumping fees to... something higher! [14:51] no catastrophic failures, just some transaction too smals, and mempool issues so far, still learning [14:52] @corby i thought that this may happen :ThinkBlack: [14:52] @corby x10? 100x? 1000x? Ballpark? [14:52] Definitely ballpark. [14:52] 😃 [14:52] 😂 [14:52] Is a ballpark like a googolplex? [14:53] @push | asset transactions are definitely more expensive to sync [14:53] yes yes they are [14:53] they are also more expensive to make i believe [14:53] 10,000x! [14:53] as some sync process seems to occur before they are done [14:53] @traysi ★★★★★ thanks for the suggestions we are going to be looking at optimizations [14:53] But, it is way slower than we like. Going to look into it. [14:53] i do not understand fully its operation [14:53] 1000x at minimum in my opinion [14:53] its too easy to spam the network [14:54] yes there has been some reports of ahem spam lately [14:54] :blobhide: [14:54] 😉 [14:54] cough cough ravenland [14:54] @russ (kb: russkidooski) we're in agreement -- it's too low [14:54] default fee 0.001 [14:54] ^ something around here [14:54] @corby yep we all are i think [14:55] waaay too low [14:55] meaningful transactions start with meaningful capital expense [14:55] though there is another scenario , there are some larger volume, more objective rich use cases of the chain that would suffer considerably from that [14:55] just worth mentioning, as i have beeen thinking about this a lot [14:55] there are some way around, like i could add 1000 ipfs hashes to a single unique entity, i tested this and it does work [14:56] @russ (kb: russkidooski) What would you suggest. [14:57] I had a PR for fee increase and push back. [14:57] Ignore the push back. 0.001 RVN is not even a micro-farthing in fiat terms [14:57] definitely around 1000x [14:57] Vocal minority for sure [14:57] ^ yep [14:57] @russ (kb: russkidooski) That sounds reasonable. [14:57] Couple hundred Fentons [14:58] right now an asset transaction is 0.01 of a penny essentially [14:58] 1 RVN would work now, but not when RVN is over $1. [14:58] yes exactly [14:58] Hi. Late to the party. [14:58] We are also talking about a min fee. The system will auto-adapt if blocks fill up. [14:58] im thinking tron, some heavy transaction use cases would fall out of utility use if that happened [14:58] so whats the thinking there [14:59] is there a way around the problem, bulked ipfs hash transactions? [14:59] 1000x would put us around btc levels [14:59] maybe a minimum 500x? [14:59] @russ (kb: russkidooski) Agreed. [14:59] <[Dev] Blondfrogs> It is time to wrap it up here. Everyone. Thank you all for your questions and thoughts. We will be back in 2 weeks. 😃 [14:59] Small increase and review. [14:59] Thanks all! [14:59] Cheers. [15:00] yeah sorry for 1 million questions guys hope i didnt take up too much time [15:00] cheers all 👍 [15:00] Thanks everyone [15:00] Thanks everyone for participating!!! [15:00] That is what we are here for [15:00] 100x-500x increase, 1000x maximum [15:00] 🍺

submitted by Chatturga to Ravencoin [link] [comments]

[ELI5] Extracting Privkeys from QT/Core

We have a constant stream of people coming back after abandoning Dogecoin and the sub in 2014 when the price fell. These people all have old versions of QT and are now basically trying to recover their coins, presumably to cash out and abandon us again. This is causing strain for the network, as far more people are trying to leech blocks than seed them.
The thing is, none of this is necessary. Especially if you're just going to dump coins. With resources such as all you need are your private keys, and you can create, sign and broadcast transactions yourself. No client required, let alone one as resource-hungry as QT.

"So, how do I get my keys?"

First of all, lets talk about data management. The overwhelming majority of coins are not lost through theft, especially direct theft of wallets (as distinct from wholesale thefts/scams/implosions like Moolah, GAW, MtGox, Cryptsy, and even our own beloved Dogetipbot). Most coins are lost because people forget about their wallets and do silly things like reformat hard drives, lose passwords and so on.
So, everyone should have a wallet list. Here is a sample bit of HTML that gives you a page with two columns of wallets, one for local wallets you would withdraw coins to, the other the third-party wallets you would deposit coins to third parties through (do note that many services use temporary addresses generated for deposits which expire after 24h or so). A page like this is how I manage my 100+ wallets, and I have copies on my network and hidden online. Such a page makes it easy to at least keep track of all your wallets, for a trivial amount of work to set up.
 Sample - Twitter Fr DFXXz9gq3WkgJaHn9tXRChMhFQcwm4Y251 To DByYgzd4ec5Ku9vPag8XqoBfyRpsoj8Xs3 @TipDoge Sample - Backslash Fr DSDyv83VC1QtEnmJ4ATKFn5Sw3iC12VLmX To D9MsxSyJe5Mq7fWFRpC7zQQt1gexHccN4w Backslash To DJ3GL68kw8vh99RvxnEmQKE8A3cWRoEEqo Backslash Faucet Sample - To DE5QamzWVnxK2HmCS61cUsrn9iwgTArunU 

"OK, great, so now I have a list of my wallets. Now what?"

Now you're going to need the private keys for each of those wallets. Obviously you're not going to store these in a public place though. So you will need a separate file, which can just be plain text. Copy each of those addresses into it.
Now go ahead and fire up QT. If you haven't synced it in 3 years, its going to take forever, but that doesn't matter. You don't actually need the blockchain for this, so you don't have to wait for it to catch up.
Open up the console which is in the Help menu. Then give the command dumpprivkey with the wallet address you want the key to. Then use the up-arrow key to bring that command back, replace the address with the next one, and keep going until you have them all.
It will look something like this:
 13:05:18 Welcome to the Dogecoin RPC console. Use up and down arrows to navigate history, and Ctrl-L to clear screen. Type help for an overview of available commands. 13:11:06 dumpprivkey D9xDcRthB6XP4vRGqiyKdDfVJ7CWhYuBBi 13:11:06 6KEcssuq1wWUrFVmMF8yDxHuAdQMiRezz53zDxADLmyoXnix7iM 13:12:00 dumpprivkey DUDARNrGHVTFcCgriwRWgDQJPKDuDQr9jg 13:12:00 6JNk6NNFZcr49fbsD2jcTfTxFLjJKq9DHQ5JU8CYeZ2Cz6JdKMY 13:12:25 dumpprivkey DG6xnwCT6BXePaySqU85XocobZmhbJczQH 13:12:25 6JNXFv95Mp9SzehHw9jojjdxHRNPeh77qCsRbaNwJZMp9MKCAu3 
Yes, those are real wallets. But don't bother trying to steal my coins, I just generated them on and they're empty.
That's basically it. All you need to do is add some descriptions of what the wallets are, pretty up the format to your liking, and save copies in multiple, secure places, including printed out.

Remember, if you lose your keys, OR someone else sees them, you lose your coins!

If those were my real wallets above, you could use the keys and spend my coins. So obviously, don't let anyone else, especially annoying little brothers, get their grubby hands on them. But also make sure they can be discovered if anything happens to you. That's why the printed copies... nobody is going to go trolling through your porn or warez collection on the offchance there's something valuable in there. But they will look in your safe or wherever you store other important documents. Just be sure to leave a note as to what they are and how to use them. Remember the woman who came here a couple years ago who had found a USB stick with 110 BTC in a locked wallet.dat on it from her dead husband? I sometimes wonder if she ever got the money. Don't be her. Or him.

"OK, great. Now I have my keys. What now?"

Well, you can spend coins using from any wallet you have the keys to. First step is to choose the network. Dogecoin (mainnet) obviously. Then go to Transaction in the +New menu. Enter your address and hit the Load button. It will pull in the first 100 transactions. Now enter the address to pay, and the amount.
Note the Transaction Fee box!
You want this amount to be zero. Depending on whether you're moving coins to another of your wallets to consolidate them (a very good idea.. go read the UTXO ELI5, which you will find a couple pages into - Yes, I'm going to make you work for it, cos there's tons of useful stuff there you need to know), or paying someone else, you may want to select which inputs to use.
Once you're happy with the transaction, go ahead and submit it. You will now get a block of text, which is the raw, unsigned transaction. Copy this. Go to the Sign tab. Paste it. Add your private key and Submit to sign it.
After a little bit, you will get a signed transaction. Copy it. Go to the Broadcast tab, paste it and hit Submit.
That's it. It should go into the next block in a minute or two. Yes, even without paying a mining fee. Our network is so lightly loaded that there are no contention issues like the Bitcoin people have to put up with.

"That's it? So why do I need QT?"

You don't. The process above is all that's involved in spending coins. Everything else is window dressing. So there is no need to run QT, or any other client. Oh, and since you can download the site and run it locally (mostly offline), there is no security issue beyond the usual keyloggers/spyware that can compromise anything. And by knowing how to do this, you are much better protected from accidental loss than someone who blindly trusts black boxes they don't understand.
Oh, one final thing... if you really want to help the network by seeding rather than leeching, go ahead and run a full node. Instructions are in that link above. AND you may want to help seed the bootstrap file torrent from a couple of days ago. Just because YOU don't need it, doesn't mean others don't, right?
submitted by Fulvio55 to dogecoin [link] [comments]

KoreCoin v2.0 [KORE]New ERA - VOIP WALLET -100% ANON - 100% PoS - PoBAnon

A Kore Twitter Campaign has been activated at! Take 30 seconds, earn some free coin, and support Kore in the process! Check it out at:
New block explorer:
Important Mandatory Update: Please bear with us while we await the new OP page/wallet release.
IF you don't have these latest wallets installed we are requesting you update them ASAP. There are some old wallets out there causing issues with the staking.
1-Windows Wallet standard: Windows Wallet with updated Peers.dat file so the wallet will sync easier.!lBlGmL7R!UW-lzmtfHa1OeC0dn_D18jq4KXejST32oyeNApQVqOE Current peers.dat file to get the wallet to connect/sync.
Use the link below to go to the "Kore Support" thread and replace your peers.dat file with the most current one uploaded.
Peers & Nodes: Current Peers: 43ddpe3mgqu6im72.onion rdglputx5w4hsahq.onion dqdwqq6siopitcnx.onion imtxip6b3epoydq7.onion c7golffjz4qcomts.onion mtxip6b3epoydq7.onion nvye5tclv4gsp4qz.onion bqr3uvoqn7afaftn.onion oxk3k46qpyewkuha.onion xjmdb3rrlp5mjsor.onion nelcm3y2yuwkubww.onion pgtp5zcbhzivkdhy.onion eldldqcauon5fjye.onion ygjegzdh56fuielv.onion fy225sytea4x2d5d.onion bo5whi6igdfujywm.onion 7qmaqqvbcgkz46wy.onion dv6eypxco54m2yil.onion dxtf2khtvtrlt5x3.onion 3qtpdtcoeajm2u6u.onion 56ozxvu5gcljant6.onion 5svpy4wrwtjdoqb6.onion 7kerj4xmvc7pgvf4.onion gfnmkcixbz7nekgr.onion xsuhp3s4nwciyopc.onion ua3np4ut2zxubqow.onion ap2u6b77yi5esd72.onion rnwgen4v5vvgyrui.onion suifi73rcv6xptco.onion 5lxnox7rk77qemdo.onion uuvjof5votogzak.onion
OLD: addnode=xjmdb3rrlp5mjsor.onion:28556 addnode=dxtf2khtvtrlt5x3.onion:28556 addnode=oxk3k46qpyewkuha.onion:28556 addnode=266polqfpc22sn4b.onion:28556 addnode=tvmhij7hyrqir5y2.onion:28556 addnode=culqahwoixao4zgp.onion:28556 addnode=copqf7fhnf4ve2pz.onion:28556 addnode=xx37ikzbjib5wdhm.onion:28556 addnode=ua3np4ut2zxubqow.onion:28556 addnode=iqtgfnjunu4ixdqq.onion:28556 addnode=gpy2co2ik7jn7woy.onion:28556 addnode=c7golffjz4qcomts.onion:28556 addnode=5rpb5tuybqdfmtbk.onion:28556 addnode=urc3dssckhvsbswb.onion:28556 addnode=gfnmkcixbz7nekgr.onion:28556
Up to date Bootstrap and instructions Here: NOTE: Use at your own risk...
KoreCoin_OSX_2.2.1.dmg - no VoIP:!LN9UTIiB!keSf4dFGeF0qlMQ5xmXNIAZIpdEl8mwTvtJLmYbLRoI
2-For a custom Linux Version go to end of post: Version: 64 bit Ubuntu Linux 14.04 LTS Trusty
3-KoreCoin Website:
4-Source Code - GitHub Link:
5-KORE Block Explorer:
6-Please stake some coins to support the Kore Network. If you are new to Kore PM me for some free coins to stake.
Thanks to: "bearishtrader" "Here is my Ubuntu Linux build of KoreCoin 2.0 staking wallet (no VoIP): Version: 64 bit Ubuntu Linux 14.04 LTS Trusty"!Nk110QaT!yuf_cVCyKtXoJufgi3kJk6VcvsC4r92WP4ZMtnBrbeY
Prerequisites (Needs boost 1.55, Berkeley db4.8++): sudo apt-get update sudo apt-add-repository ppa:bitcoin/bitcoin sudo apt-add-repository ppa:boost-latest/ppa sudo apt-get install unzip qt4-qmake libqt4-dev build-essential libboost1.55-all-dev libssl-dev libdb4.8++-dev libminiupnpc-dev libminiupnpc8 sudo apt-get upgrade
unzip chmod u+x korecoin-qt korecoin-qt
Then exit and replace the .KoreCoin/peers.dat with the one above
Re-launch wallet
NOTE: If you get a virus warning we have researched it as a false positive. You can put it to your antivirus/antimalware exclude list so its not checked. Not one person ever had an issue with malware or a virus using the KORE wallets.
With this unexpected price rise, many are curious what KORE has to offer and what the coin is about.
KORE is a project centered around security in Communications, Computer, Smart Phone and Marketplace interaction and use. There are a few other KORE Projects we cant yet announce. Lets talk a bit on the ones we're able to disclose...
1-Integrated Tor for secure transactions and staking 2-Integrated Tor browser for secure web surfing 3-KOREPBX for secure wallet to wallet and Telecom number calling and video. 4-KOREbay A unique Tor hosted Marketplace 5-Aether Krypton OS - A new Operating System based on Security and Privacy 6-KOREPhone - Our KORE branded phone to debut the AEOS also centered on security and privacy with some unique features. 7-KORE PoBA - Our end goal of the holy grail of anonymous currencies.
KORE is the first coin to integrate Tor into the wallet transactions and staking meaning your IP is not seen. KORE had also been the first coin to integrate a PBX based wallet to wallet calling service. We are presently working on the end goals of including Video Calling, messaging and making it a bit more decentralized and secure with the end goal of having it run through the Tor network. We also want to include the ability to dial regular telecom numbers. This work is in progress and some is undergoing testing.
KORE also is the first coin to work on a multi year project of an Operating system centered around privacy and security called the Aether Krypton OS.
The Operating System is planned to debut on the KOREPhone, another first.
KORE with another first integrated a Tor Browser into the Linux wallet some time ago to debut in the new release. This allows you to surf the web in privacy and security.
KORE was also first to announce the unique KOREbay marketplace which is in development. This service will be unlike many other crypto related marketplaces and have additional hosting on the Tor Network.
Our goal is to take what we have and upgrade anonymous currencies to the next level.
For now these are the projects in various stages of development and testing that we can talk a little bit about. We will not give out any road maps. The releases could start in 2-5 months or 2-5 weeks. This is about giving the growing KORE community and Investors an idea of the perceived value of what we are bringing to the crypto/public as a means of providing alternatives to choose from. There are plenty more KORE Team projects and we could possibly post a few of those once the new wallet is released in the new OP page where dissemination of information will be a little more open. Join the KORE Revolution!
Yours Truly, MikeMike
submitted by Vindyne8 to CryptoCurrency [link] [comments]

Inadvisably small full node config

Disclaimer: As the subject implies, this is about an inadvisable config. The following is of zero practical use, but like cross-stitch, may be appealing to the random few people interested in such things. Opinions on the futility of this exercise can be considered already noted. Any suggestions to make this more ridiculously small are very welcome. Obviously I'm not running my primary wallet off of this config. It's just for fun.
TLDR: Wow look, my full node fit on a 0.5 CPU with 0.6 GB memory and 25 GB drive... yeah for me!


I used to run a full node a good ways back, but stopped when the old 3rd string laptop I was using to run it was having drive issues. Still the early interest paid dividends as the price has gone exponential. Missing the good ol' days, I wanted to run another node, but really didn't want to do it on any of my work or lab units. My company took a hard stand years ago to prevent interns from mining on spare HW, so running even a full node on my corporate gear is kinda a capitol punishment. Round about this time, I got some spam for some free VPS service for a year. The promotion were really (I mean really wimpy VPSs). Crappy VPS + bitcoind performance tuning = my kind of waste of time.


My goal (perverse though it may be), is to get bitcoin or other forks running in very small VPSs. Maybe some of the tuning parameters could be used for a docker container or some whipy SOC. The system I was targeting has 0.5 CPU, 0.6 GB of memory and 25 GB of disk.


I found some interesting things out along the way that may be of interest to people tweeking bitcoind.

dbcache limits

Since I don't have the requisite memory required to run the node, I've limited memory using the dbcache parameter. Settings range from 100 to 150 depending on what other settings I have in place.

0.15.1 mallocs

I don't know what changed in 0.15.1 but it seems much more memory hungry than previous releases. Throughout the tuning process, I continually had either bitcoind quit due to memory allocation failures (logged in debug.log), or the kernel oom_killer take maters into its own hands (logged in /valog/syslog). This looks very similar to an issue that was logged against 0.14.0 that was patched in 0.14.1. My ultimate solution was to downgrade to 0.14.2 which seems to work great.

prune compromise

My initial thoughts were to use prune=550 to use the least amount of disk space possible. I found out that even on 0.14.2 this causes memory to fill up quick. I found making the pruning less aggressive with a setting of prune=10240 seems to be a good compromise for what I need done. This could possibly be an observation error, but the results seemed very reproducable.

blocksonly avoidance

I had thought to save some memory by using blocksonly. For some reason, on 0.14.2, this causes more problems than it solves. I had a hard time finding any config where blocksonly would work. Surprisingly, maxmempool=5 does effectively the same thing for the miserly cost of 5MiB of memory.

serial consoles

Seems ridiculous, but on my VPS, if bitcoind was running full speed, I would have a hard time connecting through SSH. There were other SSH clients and connection methods that seemed to work better. By far the quickest connections when under heavy utilization was to connect directly to serial ports. I wrote a small snippet to enable extended serial console on my systemd install.

canary log

Since logging into my system gobbles up memory, I wanted this config to be as low-touch as possible once in motion. After tooling up the serial ports, I found all the system log messages where peekable without logging into my VPS through my VPS provider. I wrote a small canary script to simply chirp to the serial port every 5 minutes to confirm that bitcoind was indeed alive and kicking.


I made a few scripts during the process as the needs arose. They are very utilitarian, and could do with some major overhauls, but they did what I needed done at the time I needed it.

Final config

Here is my final config, that is still syncing, but seems to be stable on 0.14.2
/usbin/nice -n 15 bitcoind \ -dbcache=115 \ -prune=10240 \ -maxmempool=5 \ -daemon /usbin/nohup $HOME/ $1 300 $USER >/dev/null 2>/dev/null & cPid=$! sudo /usbin/renice -n -5 -p $cPid echo "Canary @ $cPid" 
Memory utilization while syncing seems to be at about 400MiB. Once I'm synced, I expect to retune for dbcache=60 and maxmempool=60.
Projected full blockchain sync completion in (gulp) 30 days. CPU utilization is currently reported between 30-60% but my provider offers boost periods where they unmeeter the VMs. I've gotten it up to 110% on their dashboard, for what its worth.
I'm well beyond the word limit so I'll drop off here, but I'll eventually put the snipits in a github repo in the near future.
PS If anyone knows of some free VPS or Docker hosting services, please chime in.
EDIT: s/VSP/VPS/g - lysdexia
submitted by brianddk to Bitcoin [link] [comments]

Syncing bitconnect wallet with network. Bitconnect wallet (not sync) *fix*. How to Setup and Sync Bitconnect-Qt Wallet on macOS Bitconnect Wallet Connection Problem Bitconnect QT Wallet on MAC - NOT SYNCING - FIX!!! How to Repair a Qt Wallet that won't Sync. - YouTube

But the wallet should only be for normal use. It cannot be used to mine Dogecoin, as the wallet will become slow and unresponsive if used this way. Dogecoin Core on the other hand, downloads the entire blockchain. Its initial sync is significantly slower compared to MultiDoge, and it takes up a lot more space. But this comes at an advantage. A new bitcoin-wallet tool is now distributed alongside Bitcoin Core’s other executables. Without needing to use any RPCs, this tool can currently create a new wallet file or display some basic information about an existing wallet, such as whether the wallet is encrypted, whether it uses an HD seed, how many transactions it contains, and how ... Digital money that’s instant, private, and free from bank fees. Download our official wallet app and start using Bitcoin today. Read news, start mining, and buy BTC or BCH. You can use them by supplying -wallet arg to bitcoin-qt For example, if you are on linux: Create 4 wallets by starting bitcoin core, stopping bitcoin core and then renaming the wallet.dat in your ~/.bitcoin folder (then repeating the process). I spent a ton of time today trying to get Bitcoin-Qt to sync using the bootstrap.dat file and could not get it to work. ... It goes through the blockchain to find transactions that are missing from your wallet. It is only very rarely needed (like when you manually changed things in wallet.dat). ... Meaning of 'eben' and how to properly use and ...

[index] [5601] [28469] [16372] [5323] [32318] [3457] [12358] [17448] [3359] [7776]

Syncing bitconnect wallet with network. Bitconnect wallet (not sync) *fix*.

How to Sync Your Bitcoin or Dodgecoin Wallet ... This video talks about what syncing you Bitcoin or Dodgecoin Wallet means. ... Your DogeCoin Wallet Safely and Securely (Or any QT Client ... Here I walk through how to repair and resync a PIVX Qt wallet that won't sync with the blockchain. Purchase a Ledger Nano S: Quick Fix Bitconnect QT Wallet Out of Sync 🖥️ Mac OSX - Duration: 5:30. Nad Daniels 2,327 views. ... Bitcoin Daytrader 3,823 views. 16:16. How to Repair a DEAD Computer - Duration: 37:05. Getting your Bitconnect QT wallet to sync ... Bitconnect QT Wallet Out of Sync 🖥️ Mac OSX - Duration: 5:30. Nad Daniels 2,325 views. 5:30. Install, Backup And Restore A Bitcoin Wallet. ... How to make your Bitconnect QT wallet sync on Mac The BS Crypto Show ... Bitconnect QT Wallet Out of Sync 🖥️ Mac OSX ... How to install Electrum Wallet for Bitcoin (BTC) on a Mac ...