Sorry for the confusion. As I re-read this, I articulated things poorly. Just wanted to clarify things, as not to confuse other people as well.
The 1 PPS / 10 MHz input is something entirely different - this functionality, now in master, allows the on-board VCTCXO to be tamed by supplying 1.8V 1 PPS or 10 MHz input source to pin 1 on the mini expansion header. The purpose of this is to minimize frequency error and to allow people to re-calibrate their device. We'll be working on a blog post about how to do this with a COTS GPSDO.
The synchronized (or "triggered") capture functionality up in that development branch allows the mimo master to gate sample reception/transmission on all of the slave devices; this is the functionality I think you might find particularly useful. This is done using an I/O pin on the same mini expansion header. What I feebly tried to articulate was that this conflicts with the aforementioned pin assignment, since these two things were developed in parallel; we will change this pin when we merge this trigger-based.
What is currently not in the active "TO DO" list is having the bladeRF set a supplied timestamp value on the next PPS pulse. However, I will talk to the guys about what it would take to get this into the queue.
Hopefully that sheds a bit more light on what's to come. I'll try to touch base with you once it's all ready, and will be looking forward to future developments in your projects!