Topic: Bitmark - page 76. (Read 622213 times)

Thanks Mark, great to see steps forward on the roadmap
https://bitmark.aha.io/published/4457ddb73f8f65e4b34ace9b319a4942?page=1

Bitmark 0.9.3 Released

This version of Bitmark Core aligns with Bitcoin 0.9.3, including post release updates.

It also includes Bitmark specific changes most notably the private key format has changed, a converter can be found at http://bitmark.co/brain to swap between old and new keys.

Existing wallets, and backups will continue to work as expected, only exported keys / cold storage keys need to be converted before importing them to v0.9.3.

Release and downloads for Windows, Linux, and Mac: https://github.com/project-bitmark/bitmark/releases/tag/v0.9.3

Changes:

• Private key version change to 213 to align with common third party tools.
• Seed Nodes and Checkpoints updated.
• Make -proxy set all network types, avoiding a connect leak.
• Refactor Alert to use static methods.
• Avoid a segfault on getblock if it can’t read a block from disk
• Add paranoid return value checks in base58
• Don’t poll showmyip.com, it doesn’t exist anymore
• Add a way to limit deserialized string lengths and use it
• Increase IsStandard() scriptSig length
• Avoid querying DNS seeds, if we have open connections
• Remove a useless millisleep in socket handler
• Stricter memory limits on CNode
• Better orphan transaction handling
• Add -maxorphantx= and -maxorphanblocks= options for control over the maximum orphan transactions and blocks
• Check redeemScript size does not exceed 520 byte limit
• Ignore (and warn about) too-long redeemScripts while loading wallet
• fix ‘opens in testnet mode when presented with a BIP-72 link with no fallback’
• AvailableCoins: acquire cs_main mutex
• Fix unicode character display on MacOSX
• key.cpp: fail with a friendlier message on missing ssl EC support
• Remove bignum dependency for scripts
• Upgrade OpenSSL to 1.0.1i (see https://www.openssl.org/news/secadv_20140806.txt - just to be sure, no critical issues for Bitmark Core)
• Upgrade miniupnpc to 1.9.20140701
• Fix boost detection in build system on some platforms

Pfennig 0.9.3

Pfennig has also been updated to align with both Bitcoin v0.9.3 and Bitmark v0.9.3.  Source can be found at https://github.com/project-bitmark/pfennig


More

Bitcore, Insight-api, and Insight have all been updated recently.
A pull request with BTM support has been submitted to brainwallet.org.
http://bitmark.co/brain/ has been updated to produce both v0.9.3 and previous version private keys.

High difficulty and low profitability, so very few miners. So production is slowed. It's not too much of an issue yet as we haven't rolled out any of our services yet so demand for Bitmark is low right now. And the benefit is that production of BTM is very low, which is helping to restrict supply.

What is wrong with the network? Shouldn't there be one block every 2 minutes? Right now there is a block every hour at most and they are nearly empty....

That's great news.

In a DAC no one is expected to meet every milestone, in fact, the autonomous nature is that no one should feel expected to contribute at all.  That people step up to the plate and volunteer, time, code, donations and mining is a remarkable thing.

The project plan looks very cool and well put together.

In all projects, unexpected things come up, and it's great that the community has been able to get trough these challenges.  

However, I will note that the first release was anticipated on 21st Nov. and we didnt have any word until the 26th, 5 days later, that it was going to be late.  Indeed, those of us that waited were told on the 21st that it the release was still expected that day.  While I dont think it was a particularly mission critical release, in fact I still am unclear what MEWA is, there was general excitement in the community as it would have been the first lines of actual code we got to see after several months of waiting.  Until then it's been on track for either 2 days away, or the end of the week, for about 10 weeks, rolling.  I think it's unfortunate, because had this not been the first lines of code of core marking, I think there would have not been so much excitement and expectation.

I know this is an alt coin and such things, if not worse, are quite normal.  However, this track record has left considerable doubt of the future claims of the project, even to some of the most staunch supporters.

It's really encouraging that people are taking a the time to offer transparency and expected milestones.  But it would be helpful for everyone in the community if those milestones are realistic, and if some consideration is shown when not able to meet them.  I stress that this is not a must, and there is no obligation here, but this is a general code of conduct consistent with the very highest quality, and long term successful open source projects.

Wanted to take a minute to express my grated toward the Bitmark Community.

Y'all are truly an amazing group of people. Looking back, Mark was a genius to structure the OP in such a way, as it mitigated noise and promoted the healthy growth of a community of like minded people. As Mark stated, we had an urgent matter within the community. Thankfully, we were effectively able to impact the life of an esteemed member of our community, half-way across the globe.

Additionally, the timeline has shifted to the right and the next milestone looks to be on target for this weekend.

Y'all have a great week, Happy Thanksgiving and enjoy the holidays...Don't forget to spend time with the people you love. 

Thank you for the reply! And thanks for the link. The inuit python program is a bit above my head though...

This generator creates private/public keypairs for the Bitmark network, it does not as yet provide BIP-38 encrypted paper wallets. I'll add a task to create one to our queue, community development of such items is also welcomed.

In the mean time we do have inuit which works as an encrypted cold storage solution.

Due to unforeseen circumstances, we had to shift focus to resolve some real world issues for a members of our community over the past few days.  As such delivery of the multi-user wallet api is now postponed until Friday, and the Marking layer over the weekend.  The music curation service is an externally developed project and is still scheduled for the 15th December.  Additionally, we hope to have UI designs from them for release early next week.

Thank you for your continued support, and special thanks to those in the community and on the ground who helped us address the situation, it's an honour to work with such exceptional people.

How do I use the brain wallet generator (http://bitmark.co/brain/) to make an encrypted paper wallet? Is it possible? Is there a paper wallet generator for BTM?

Thanks, I certainly appreciate the kind comments.

Aha! is just one of the tools the Bitmark Team has at its disposal…we may have a few more under our sleeve. 

Furthermore, Mark has been hard at work pushing quite a few commits forward.   

Wow never seen a roadmap like this
Good work

+100 !

Great work you've been doing there.

Yeah, before it was more of a minor inconvenience for people and now it's more than that. We're discussing the issue in slack now.

I was thinking of sending some BTM to Bittrex to raise some fiat to pay the bills. Umm. Bad idea.  The nethash has found 1 block in the last 24 hours.  I'm guessing that Bittrex requires at LEAST 5 confirms.  That is the best part of a week. 

I can't sell the coin.  If I buy the coin it could take up to a day to land in my wallet at 1 confirm....  Guys, this is not a sustainable situation.  Yeah, some merchants will take it with zero confirms but how does that help a miner pay his electricity bill?

With time and as the project moves forward, so will demand. Because the supply is low, price will go up. Price goes up, more miners. More miners = stable nework.
So in my opinion it's perfect as is.

Keep up the good work!

Thank you to Medic for his hard work and help managing the project.

I'd just like to say that the mining concerns have been noted, we have to viable proposals, and potentially a chance to implement one of them in a different coin next week to give it a try before we adopt it properly.  for now the BTM supply is very low, in fact we hit 50% emission earlier today.  There should be 1.85 million and we have less than 924k so far, some days only 100 created out of a possible 14,400!  The mining is tough, but limited supply is doing it's job for now.

Back to work.

Thanks for sharing, that's a great roadmap.

thank you for sharing! this is great

Good Day,

Everyone, within our ever-expanding Bitmark Community, should be well aware of the direction our Project is going. The discourse and contributions made over the past few weeks have allowed us to refine our focus.

Mark shall develop the fundamental aspects of the Marking. If there are any aspects of this project that you feel compelled to contribute to, we appreciate and encourage your assistance as we drive forward with development.

For a detailed Roadmap to Development - Please follow this link

https://bitmark.aha.io/published/4457ddb73f8f65e4b34ace9b319a4942?page=1