Thanks for the support guys. Things are a bit hectic for me at the moment, but once I get a few things out of the way, I will likely look into some sort of limited worker using an arrangement similar to what was mentioned earlier.

A few updates:

• Merged broadcast_transaction_synchronous API addition from Steem by @ElMato (https://github.com/bitshares/bitshares-core/pull/311)
• Merged get_asset_holders API fix from @oxarbitrage  (https://github.com/bitshares/bitshares-core/pull/312)
• Merged Windows build fix from @abit (https://github.com/bitshares/bitshares-core/pull/299)
• Documented OpenSSL compatibility issue (https://github.com/bitshares/bitshares-core/wiki)
• Merged minor graphene constant cleanups from @oxarbitrage (https://github.com/bitshares/bitshares-core/pull/309, https://github.com/bitshares/bitshares-core/pull/310)
  
• Added additional seed node from @sahkan (https://github.com/bitshares/bitshares-core/pull/286)
• Merged Visual Studio compatibility fix from btsabc for bitshares-fc (https://github.com/bitshares/bitshares-fc/pull/4)
• Miscellaneous bitshares-fc cleanup (https://github.com/bitshares/bitshares-fc/commits/master)

Huge thanks to everyone who supported this worker. One of the unique things about BitShares is how decentralized its development is, and over time I've added active contributors directly to the BitShares GitHub organization. I think this plays an important part in helping ensure that BitShares will continue to improve and grow, without needing to depend on any single person. Special thanks to @abit, @ElMato, @oxarbitrage, @pc, @svk, @xeroc and any other team members for their continuing work.

Unless this worker gets voted back in at some point, all of my focus is now dedicated to the upcoming Soledger blockchain project. I will make an initial announcement on the project after development has progressed a bit more. The details may change, but my hope is that the project can directly benefit the members of the BitShares community. If possible, I hope to also give an extra bonus to those who directly supported myself and Soledger either through this worker, or with other contributions to the project in the future.

As always, anyone still feel free to contact me about helping organize things on the GitHub or forum, or other related issues to help the improve the community.

@flaka I have added a Hindi section and made you moderator. Let me know if you want to adjust this to include all India instead of only Hindi.

@educatedwarrior Do you still have the original backup made using v0.4.23.1? And to be clear this is a backup JSON you are recovering from and not an existing full wallet directory from that old version? And you are sure you did not make any further transactions after this backup was created so it should contain all your keys (including potential AGS/PTS keys that were never claimed)?

I'm looking at some of the old wallet releases and it seems like there might be a separate issue with the format of certain wallet records changing in later versions. These records should have automatically updated when upgrading--but to be safe I'm thinking that for very old backups it might help to:

• Install v0.4.24.1, import and unlock the backup wallet (you might see a wallet format upgrade message)
• Upgrade to v0.6.2, open and unlock the same wallet (I don't think this step is necessary but just in case)
• Upgrade to v0.9.3c, import the final blockchain and do a full rescan following the 2.0 migration instructions

More information on where the breakdown seems to first occur would also be helpful. For example, you are able to see your expected balance at point X but cannot migrate it to version Y?

Edit: @mrbildo Sounds like you are in a similar situation with a very old wallet backup JSON? Do you have an idea of where the breakdown might be occurring when following the above steps?

This topic has been moved to Other Blockchains.

https://bitsharestalk.org/index.php?topic=24183.0

This topic has been moved to Other Blockchains.

https://bitsharestalk.org/index.php?topic=24167.0

• Fixes to re-indexing decisions and behaviour (https://github.com/bitshares/bitshares-core/commit/f13698370b9eb2d64677bad0e2bc6a52aa93f039)
• Merged upstream JSON RPC improvements (https://github.com/steemit/fc/issues/13)
• Updated seed nodes (https://github.com/bitshares/bitshares-core/compare/8c0668de367b3826c52e4217880eb8a227caadf7...cda895abd6d7a7d4556d63e31f61438f310ead9f)
• Fixed broken reference links and cleaned out old pages on GitHub wiki (https://github.com/bitshares/bitshares-core/wiki)
• Cleaned up bitshares-core GitHub branches

I am looking forward to see whether the upcoming Peerplays blockchain might have any general Graphene patches that could be applicable to BitShares.

• Merged memory leak fix by @abit (https://github.com/bitshares/bitshares-core/pull/257)


• Merged -track-account command line argument fix by @abit (https://github.com/bitshares/bitshares-core/pull/259)


• Merged get_full_accounts API enhancement by @alt (https://github.com/bitshares/bitshares-core/pull/261)


• Merged console P2P error issue fix by @oxarbitrage (https://github.com/bitshares/bitshares-core/pull/264)


• Merged new get_block_header_batch API by @oxarbitrage (https://github.com/bitshares/bitshares-core/pull/263)


• Fixed compilation compatibility with new Clang 4.0.0 (https://github.com/bitshares/bitshares-fc/commit/908762d687eccab019403189fd1d95502fb75c89#commitcomment-21919423)

• Fixed a crash in get_ticker and get_24_volume API calls as identified by @oxarbitrage (https://github.com/bitshares/bitshares-core/pull/250)

I've recently been interested in a somewhat similar model Counterparty is using to run EVM contracts off the Bitcoin blockchain: http://counterparty.io/news/counterpartys-evm-port-moves-forward/

Quote from: fav on March 28, 2017, 05:43:12 PM

Quote from: JonnyBitcoin on March 28, 2017, 03:30:45 PM

Quote from: mostar on March 28, 2017, 02:20:33 PM
Hi,

I'm building a new local non English Bitshares site for my local community.
Looking for some graphic files like photoshop psd files for logos etc.
Where can I find it?

Mostar

There definitely used to be  a place where you could download all the logos that @cass made, not sure if it was on this forum, github or bitshares.org website.
Do you know where there are/were @fav

there was a link on bitshares.org, but seems that was moved

but you can google the logos etc easy

I think these links are what are being referred to: https://bitshares.org/contact/

Those materials haven't been updated in a long time though.

Since the last update I've basically:

• Merged a few bitshares-core PRs (https://github.com/bitshares/bitshares-core/pulls?utf8=%E2%9C%93&q=is%3Apr)
• Including a large API notification patch that @ElMato and @oxarbitrage have been working on for some time (https://github.com/bitshares/bitshares-core/pull/249)
• I also simplified the internal time system to help improve the consistency of the code (https://github.com/bitshares/bitshares-core/issues/76)
• Merged a few minor updates to bitshares-fc (https://github.com/bitshares/bitshares-fc/commits/master)
• Including merging an upstream feature from steemit-fc to help log the time taken by API calls (https://github.com/bitshares/bitshares-fc/commit/1f41494f360a1800fc967d647631cf64fdc549ee)

As mentioned previously, there is not a whole lot of core/fc development activity at the moment, so I think roughly monthly updates strike a good balance. Again, part of the intent of this worker is to be a clearly defined agent that can encourage and integrate contributions, but while ensuring that the stability of the network does not suffer while doing so.

This worker is unlikely to make big enhancements or other potentially nonessential upgrades on its own, but if there is a specific issue really hurting service integration or usability, of course let me know.

Shoutout to @oxarbitrage, @ElMato, @svk, and TheTaconator (@Taconator ?) for their patches or other work!

Quote from: nomoreheroes7 on March 19, 2017, 10:13:56 PM
Will trade DIGNITY for KARMA.

PM if interested.

LOL

Quote from: Permie on March 20, 2017, 06:30:44 PM
Doesn't a 'Karma' type system just encourage crowd-pleasing nonsense?
Smiting? Someone is always going to have an unpopular opinion on here, and sometimes they are going to be proven correct. We shouldn't be burying this type of content, or discouraging it.
The "Only upvote on merit and not just because you agree with it" policy didn't work at all for places like Reddit. Why should it here?

Yeah I feel the same way about Reddit and similar systems. The difference here is that the value has no direct effect on the order in which posts get displayed.

I've got no strong opinion either way, just considering as an experiment in whether we could develop an additional set of data points to help gauge community opinion, which has always been difficult to do.

Since the forum has no tradition of voting like this and it is unlikely to get traction, and since there is some good argument against, I have disabled it again.

As an experiment, I've enabled the SMF Karma feature with the following settings:

I've been wondering about the possibility of a noninflationary BitShares clone--maybe snapshotting only "active" BTS accounts--and with some features stripped out but leaving the DEX (plus maybe some parameter tweaks) and seeing how it might compete.

Not directly comparable, but I think @tonyk had a crowdfunding-based similar idea at one point: https://bitsharestalk.org/index.php/topic,21558.0.html

Soledger is mostly busy with a separate project for now but it's something I'd consider exploring later down the line if there was community interest.