Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 1347. (Read 4671575 times)

Whirlwind missives!


Jun 2nd

1.   New Logo + branding pack
2.   Repository redesign
3.   Begin website enhancements
4.   live discussions join us on Freenode: #monero for general chat, #monero-dev
5.   MRO changes to XMR to satisfy ISO 4217

Dev diary

1.   Added missing RPC methods
2.   0.8.8 changes to prevent dust attack on block reward
3.   Begun work on documenting the code and providing architecture overviews
4.   Understanding and examining the cryptonote protocols
5.   POW hashing optimisation to improve syncing times and pool verify times
6.   Lucasjones miner optimisation work


Jun 10th

1.   New feature announced deterministic wallets based on mnemonic seed
2.   XMR listed for voting on Mintpal
3.   RPC based Qt GUI wallet

Dev diary

1.   Further RPC work on simplewallet
2.   Added new seed notes
3.   Further code review and implement Doxygen for commenting and code understanding


Jun 18th

1.   Hit number one on mintpal voting list
2.   Begin peer review cryptonote whitepaper
3.   Initial work done on transaction splitting
4.   GUI wallet a lot of work to be done yet and Monero core issues to be resolved first

Dev diary

1.   TX pool handling fix to address high number of orphans
2.   Auto split is now ready for test


June 27th

1.   XMR added to 2 exchanges BTER and Mintpal
2.   White paper review continues http://monero.cc/downloads/whitepaper_annotated.pdf
3.   Bug fix restoring a deterministic wallet and old transactions
4.   Stabilising Monero, pools, merchants and exchanges
5.   Auto splitting ready for release

Dev diary

1.   Slow_hash huge changes to add AES-NI
2.   Major daemon overhaul in progress; windows support to follow
3.   Simple wallet split to Simplewallet (CLI) and RPCwallet (standalone RPC daemon)


July 6th

1.   CryptoNote peer review continues
2.   Auto splitting is now in the main code base

Dev diary

1.   RPC wallet ready for test


July 13th

1.   GUI’s received and bounties paid. Won’t be directly integrated yet
2.   CryptoNote white paper review is coming to close
3.   Begun work to re-implement the mnemonic word list in other languages

Dev diary

1.   Core major work begin to Implement an embedded database
2.   I2P focus moves from libi2pcpp to i2pd. Focus on persistent connections


July 20th

1.   Begun reviewing the implementation of CryptoNote following the white paper review
2.   Embedded database work in progress the hope is to reduce ram requirements
3.   Information security specialist joins the team
4.   German word list complete now moving onto Portuguese

Dev diary

1.   Abstraction of the blockchain storage functions completing (enabler for performance testing)
2.   Daemonising Monero work is largely completed
3.   RPC wallet can now run multiple instances (where machines need to run multiple wallets)
4.   DNS seed nodes work begun that will later replace hardcoded seed nodes
5.   Exchange’s poll get_payments fix for multiple payment IDs is testing


July 23rd

1.   Monero trading pairs added to Poloniex
2.   BSD 3-clause license changes
3.   README build instructions improved
4.   Developer training for Git usage

Dev diary

1.   RPC enhancements a new Get_info
2.   get_bulk_payments developed and ready


August 3rd

1.   Launched fireside chats
2.   Begun tracking downloads 41,425 in the first 3 recorded weeks from 15/06
3.   XMR pairs rise to 5830 XMR of volume after first 12 days
4.   Monero added to coinSource Trust Index with a score of  6 out of 7 stars
5.   Build process streamlined

Dev diary

1.   Windows build script to simplify windows builds
2.   QOS developed and ready, peripherals to be completed
3.   Embedded database is proving complex, work continues
4.   Issues resolved from logs, blockheight parameter and query_key
5.   DNS seeder code available for review


August 10th

1.   First look at the gui in the first fireside chat was positively received
2.   Monero price ticker released
3.   Test environment secured and ready for continuous integration process

Dev diary

1.   Abstracted BlockchainDB functions coming together
2.   CMakelist overhauled
3.   Unit test review/creation has begun
4.   Planning migration to new servers for blockchain and client download


August 16th

1.   GUI test release available
2.   Monero broke 600 subscribers to our sub-reddit
3.   Open source Monero stratum proxy released
4.   Finalising QoS bandwith control

Dev diary

1.   Mingw64 / msys2 largely complete
2.   Wallet code under refactoring
3.   Abstraction and refactoring Blockchain functions ready for some performance testing
4.   QoS ready awaiting testing and then release


September 15th

1.The Monero Research Lab is an open collective academic group continuing to make papers towards the analysis and improvement of the underlying core
2. Second #Monero-Dev Fireside (Fri September 19th, 2014, at 10:00 EST)
3. Merchandise available http://www.zazzle.com/monerogear* coin team gets 15% commission
4. URS released, a Monero project written in Go that allows you to sign messages using ring signatures as part of a group
5. New tagged release, 0.8.8.4, now available for download
6. GUI work delayed due to addressing some core issues following recent events. Progress continuing
7. Monero added to Coin Swap https://coin-swap.net/market/XMR/BTC

Dev diary

1. Development branch on hold, will be brought back into sync following emergency measures implemented
2. FreeBSD Compatability: Monero now works on FreeBSD out the box
3. New Makefile target, release-static, that builds statically linked binaries for redistribution.
4. Wallet: per-kb fees are nearly complete, and will be deployed to testnet within the next week or so
5. Blockchain: Work delayed by  blockchain attacks. Getting back on track with DB work
6. Core: Devs note, all non-critical "errors" and warnings have been moved to log-level 1


October 6th

1. New official Monero forum. Come find us! @ https://forum.monero.cc
2. Working hard in the background on the codebase
3. Mnemonics system overhauled and added new word lists in Japanese, Portuguese, and Spanish
4. MoneroPulse added; a loosely distributed checkpoint alert system
5. Backup distribution system in place for recovery
6. Research Lab released Research Bulletin, MRL-0003 – around ring signatures
7. Monero now at number 2 on Cryptsy voting list

Dev Diary

1. File check pointing added;  checkpoints are always enforced regular checking
2. DNS check pointing added
3. Working hard on improving the build system so builds are easier and less problematic
4. PoW algorithm annotated in the code and documented by dga


October 13th

1. Back-porting features and fixes added to the current codebase.
2. The GUI is progressing We hope to update the preview binaries in the next week or two
3. per-kb fees in testing. we expect positive testing results
5. Further tweaks to mnemonic system

Dev Diary

1. Further work on build environment ultimately to reduce build issues further down the line
2. Core: documentation continues, with Doxygen comments
3. DNS check pointing and configuration in test
4. mnemonic lists now support a variable trim length

 
Happy days!

Globb0

I was only looking at fake shares. I don't know about duplicates.

Fake or duplicates? Or both?

I tried this before. The miner indeed send fake shares resulting in a temporary ban from the pool.
Didn't try the last version though.

I would be more worry about the possibility of a malware in the software.
What if this miner become the vector for a future attack ?

Guys, it seems some suspicious russian proprietary miner kachur is very popular already. I'd like to say that this mining software seems SCAM. I banned several miners after I found duplicate share vulnerability and all miners spotted in logs with attempt to submit duplicate share were using this software. Stay away from not trusted developers, there is no even BCT thread for this miner.

If you are trusted person, we can test this miner in isolation, I'll run test pool and can give you early binaries, because after vulnerability fix they probably deleted duplicate submission functionality.

They're in there too.

Great stuff guys.
Missed perhaps a reference to the quick deployment of the FUDbuster technology.  

Monero Monday Missives

October 13th, 2014

Hello, and welcome to our fourteenth Monero Monday Missive!

Major Updates

1. The database effort is ongoing, and is currently playing a little bit of catch-up back-porting features and fixes we added to the current codebase.

2. The GUI, too, is progressing at a slightly reduced pace. We hope to update the preview binaries in the next week or two.

3. We are working hard on solving the static build issues to tag and release updated binaries. If you require any of the more recent features it is compile-only at this stage.

4. We are happy to announce that per-kb fees is going to be deployed to testnet over the next couple of days. Barring any major complications, we expect positive testing results, and are hopeful that mainnet can move over to per-kb fees within the next two weeks.

5. A few other things undergoing testing are: parallel support for MSVC 2013 as a build environment, minor tweaks and improvements to the new mnemonic system whereby English words now match on the first 3 letters and not the first 4, asynchronous DNS checkpointing, and support for long / blob hash checkpointing on both the file and DNS side.

Dev Diary

Build: initial work has started on reworking the CMake environment so that it is consistent and extensible. This will reduce build issues further down the line.

Core: per-kb fees are done, and are being deployed to testnet. If you are mining on testnet you don't have to update to that fork/branch, as we want to see more real-world results with both fixed-fee and per-kb miners.

Core: documentation continues, with Doxygen comments now added to the serialisation functions

Core: DNS checkpointing is now asynchronous, and doesn't prevent blocks from being received (in testing)

Core: file and DNS checkpoints now also support blob hash (longhash) checkpointing (in testing)

Wallet: mnemonic lists now support a variable trim length (instead of the previous fixed trim length). English is 3, the rest are 4, and the old English wordlist doesn't really conform to the trim length rule (in testing)

Until next week!

- updated by fluffypony

Could someone please point me in the direction of instructions for how to perform the equivalent of the below for monero?

The line below doesn't seem to return the commands I would expect.

Thanks.

There are many in fact, I'm privy to a few.
But pre-announcements are not always helpful to completion of offerings.
You'll have to wait for specifics on works-in-progress (at least for my efforts), but maybe someone else wants to talk about theirs?

Correct. Also, the time stamps come from pools (in the case of pool mining) and given that most of the mining is currently on pools, if one or two pools have the their clocks set wrong, there will consistently be blocks with incorrect timestamps. This is normal and harmless.

Although not required, if you are running a pool, it is probably better to enable NTP and avoid this issue.

Are there any work in progress XMR in-use services except Crypto Kingdom?

Give him some harder questions dude.

As I understand it the time stamps are from the miners.  Being that every miners' clock is not in sync causes this.  It has no effect on the network.

Did I pass the test?

May be so, but I'm weighted sufficiently in Monero. I just wanted more to average down more.

2.85mBTC is cheap, even 3.5mBTC is cheap. I think we have a good time to buy more.

It's 0.0028x still... :-)

Come on, coins are still cheap.

and say i missed that too.....

Devs - are these minor issues, business as usual?



block timing out of sequence
blocks with the same time stamp
-----



-----


They seem to be within the boundaries of acceptability. Just wondering, just in case.

(not posted here in any particular order)