BIPs are either &quot;standards track&quot; (affects everyone, represents consensus), &quot;informational&quot; (ie basically just summarizing the authors viewpoints on things) or &quot;process&quot;. <div><br></div><div>My point is you can&#39;t have a credible standards track BIP until something has been implemented end to end. I don&#39;t think it&#39;s a good plan to design these things in isolation. You&#39;ll end up with bizarre user experiences because of technical decisions taken months earlier that are now hard to reverse. A working end to end implementation gives you the confidence to say, yes, this is how it should work, because here&#39;s the demo and you can see it works very well and the code is clean.</div>
<div><br></div><div>If your BIP is informational then no problems, but I don&#39;t think there&#39;s much point in informational BIPs to be honest - it&#39;s easier to just write an email or forum post summarizing your views on things. If you find it a useful framework to write your thoughts in that&#39;s OK, but don&#39;t expect implementors to follow what&#39;s written there just because it&#39;s a BIP. It carries no more weight than any other document would.</div>
<div><br></div><div><br></div>