development
  • Alex The Great ish can't give a clear probability but looking at the current issues we face when compiling for the Mac ecosystem (M1 and Intel) and the solved status of the tracked issues on the Bitcoin Github in the codebase version we are going toward, I expect it shouldn't be too big of an problem to tackle.
  • BlockMechanic New version late tomorrow or wednesday morning
  • BlockMechanic 😩
  • BlockMechanic bad day, did nothing.
  • Crownfan do we expect qt for mac to be operational again after this release?
  • Luc Yup, I'm using that "winbloze crap" 😉 Thanks for the steps.
  • walkjivefly Assuming you're using that winbloze crap, this will probably work: *1 fire up a QT wallet *2 make sure you have some peers and are synced (if your block number is a little north of 4606 and increasing by 1 roughly every 3 minutes (or less)) then you're probably synced *2 go to the debug window *3 `getnewaddress mining` *4 `generatetoaddress 1 <new-address-from-previous-step>` You get 100 CRW for each block you produce. Let us know if they show up in the wallet overview page because they're not showing up in the CLI. Repeat step 4 as many times as you want. If you were running a real OS you could setup a cron job to mint a block periodically. God knows how you do that in winbloze. Please don't try to mint too many blocks too quickly to avoid nasty difficulty adjustments.
  • Luc So, mining instructions anyone?
  • BlockMechanic currently working on reported issues
  • walkjivefly sounds like a good idea ;-)